Never mind - the stop/rsync/change -D/restart completely worked. Whew.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/moving-system-catalogs-to-another-tablespace-tp2014761p5726241.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
--
Sent v
Thanks so much - sounds like I have a backup option if plan A fails.
Do you or any others here foresee any issues with me doing a database stop
(i.e., "pg_ctl stop -D data") followed by one more "rsync -aP" to true up
the directory on the external drive, with finally a "pg_ctl -D
/path-to-attache
On Mon, Oct 1, 2012 at 3:08 PM, scc wrote:
> Nothing like replying to a 3 year old post, but I would like to confirm
> whether this is possible.
I haven't tried this in a long time but AFAIR this is possible by
shutting down the server, start in standalone mode with change in
catalogs allowed (po
Nothing like replying to a 3 year old post, but I would like to confirm
whether this is possible. I have a 8.4 postgres database that was originally
designed (not by me) to store a lot of BLOBS and CLOBS. We're well past the
point of doing a VACUUM FULL given the 400GB size of the thing, and are in
Hi all,
On Tue, 2009-10-06 at 16:58 +0200, Tom Lane wrote:
> Yeah, I have sometimes thought that pg_largeobject shouldn't be
> considered a system catalog at all. It's more nearly like a toast
> table, ie, it's storing "out of line" user data.
pg_largeobject in it's current form has serious limi
Jaime Casanova escreveu:
> i have just read Tom's comments and yes that question was around my
> mind to: a system catalog that doesn't behaves like other system
> catalogs and in which we want different sets of permissions (see
> kaigai san's patch about largeobject controls in which he actually a
On Tue, Oct 6, 2009 at 9:43 AM, Alvaro Herrera
wrote:
> 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
Alvaro Herrera writes:
> 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.
Yeah, I have sometimes thought that pg_largeobject shouldn't be
considered a system catalog at all. It's more nearly like
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/pipe
On Mon, Oct 5, 2009 at 10:26 PM, Tom Lane wrote:
> Jaime Casanova writes:
>> seems like the original idea was to forbid this in all system catalogs
>> except pg_largeobject, what happen then?
>
> Nothing ... nobody got around to doing anything about it.
>
ah! well, having slept a while my thinki
Jaime Casanova writes:
> seems like the original idea was to forbid this in all system catalogs
> except pg_largeobject, what happen then?
Nothing ... nobody got around to doing anything about it.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@p
On Mon, Oct 5, 2009 at 7:15 PM, Euler Taveira de Oliveira
wrote:
>>
>> db=# alter table pg_largeobject set tablespace otro;
>> ERROR: permission denied: "pg_largeobject" is a system catalog
>>
>
> [1] http://archives.postgresql.org/pgsql-hackers/2004-06/msg00835.php
seems like the original idea
Jaime Casanova escreveu:
> it seems like we can't do this. At least a get this error:
>
> db=# alter table pg_largeobject set tablespace otro;
> ERROR: permission denied: "pg_largeobject" is a system catalog
>
> but pg_largeobject seems sensible to move to another table space for
> space conside
Jaime Casanova writes:
> it seems like we can't do this. At least a get this error:
> db=# alter table pg_largeobject set tablespace otro;
> ERROR: permission denied: "pg_largeobject" is a system catalog
You can move *all* of the system catalogs with ALTER DATABASE SET
TABLESPACE. pg_largeobje
Hi,
it seems like we can't do this. At least a get this error:
db=# alter table pg_largeobject set tablespace otro;
ERROR: permission denied: "pg_largeobject" is a system catalog
but pg_largeobject seems sensible to move to another table space for
space considerations, no? are there any reasons
15 matches
Mail list logo
