Re: [HACKERS] pg_largeobject and tablespaces

2004-07-10 Thread Bruce Momjian
I have added to TODO: * Allow moving system tables to other tablespaces, where possible --- Tom Lane wrote: > Christopher Kings-Lynne <[EMAIL PROTECTED]> writes: > > With our new tablespace set up, is it

Re: [HACKERS] pg_largeobject and tablespaces

2004-06-24 Thread Gavin Sherry
On Wed, 23 Jun 2004, Tom Lane wrote: > Christopher Kings-Lynne <[EMAIL PROTECTED]> 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 t

Re: [HACKERS] pg_largeobject and tablespaces

2004-06-23 Thread Christopher Kings-Lynne
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 ... Plus pg_dump support for it :/ Chris ---(end of broadcast)--- TIP 1: subscribe and unsubscribe comman

Re: [HACKERS] pg_largeobject and tablespaces

2004-06-23 Thread Tom Lane
Christopher Kings-Lynne <[EMAIL PROTECTED]> 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

[HACKERS] pg_largeobject and tablespaces

2004-06-23 Thread Christopher Kings-Lynne
With our new tablespace set up, is it ever possible for someone to move pg_largeobject to another tablespace? Chris ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster