From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Euler Taveira de Oliveira <euler(at)timbira(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: moving system catalogs to another tablespace |
Date: | 2009-10-06 14:43:34 |
Message-ID: | 20091006144334.GH5929@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jaime Casanova wrote:
> now i think that what Euler shows me [1] is a fair compromise (this is
> to allow this only when in standalone mode with system catalogs
> allowed) otherwise we will have diferent behaviour for specific
> (random) catalogs...
>
> [1] http://listas.postgresql.org.br/pipermail/pgbr-geral/2009-March/014374.html
Hmm, I don't necessarily agree that having the system effectively shut
down for the duration of the pg_largeobject move is a good idea.
I don't agree that pg_largeobject is a random catalog either -- it is,
in fact, the only catalog in which an interesting size is to be
expected.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | KaiGai Kohei | 2009-10-06 14:46:23 | Re: Privileges and inheritance |
Previous Message | Alvaro Herrera | 2009-10-06 14:41:21 | Re: Patch: create or replace language |