Skip site navigation (1) Skip section navigation (2)

Re: pg_largeobject and tablespaces

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_largeobject and tablespaces
Date: 2004-06-24 03:53:42
Message-ID: 8545.1088049222@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> With our new tablespace set up, is it ever possible for someone to move 
> pg_largeobject to another tablespace?

Assuming that ALTER TABLE SET TABLESPACE gets in, my preferred answer is
to apply that operation to pg_largeobject.

We do need to think a bit about what the safety constraints on ALTER
TABLE SET TABLESPACE should be.  To allow the above, we cannot
completely forbid moving system catalogs.  However, it will not work
to allow moving *every* system catalog ... for instance, if you were to
move pg_class itself, things would be more than slightly broken, because
the backend could not find pg_class to learn where the system catalogs
are.

It might be that we only need to forbid moving the "nailed" system
relations, but I haven't thought it through yet.

If nothing else comes to mind, a reasonable compromise for 7.5 would be
to forbid moving any system catalog except pg_largeobject and its
indexes ...

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Christopher Kings-LynneDate: 2004-06-24 03:58:52
Subject: Fixing pg_dump
Previous:From: Greg Sabino MullaneDate: 2004-06-24 03:29:09
Subject: Re: PREPARE and transactions

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group