Re: OK, OK, Hiroshi's right: use a seperately-generated filename - Mailing list pgsql-hackers

From Chris Bitmead
Subject Re: OK, OK, Hiroshi's right: use a seperately-generated filename
Date
Msg-id 394ACB42.C87C59B8@bitmead.com
Whole thread Raw
In response to OK, OK, Hiroshi's right: use a seperately-generated filename  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: OK, OK, Hiroshi's right: use a seperately-generated filename
Re: OK, OK, Hiroshi's right: use a seperately-generated filename
List pgsql-hackers
Tom Lane wrote: So
> the thing would act a lot like the original-relname-plus-OID variant
> that's been discussed so far.  (Original relname because ALTER TABLE
> RENAME would *not* change the physical file name.  But we could
> think about a form of VACUUM that creates a whole new table by
> versioning, and that would presumably bring the physical name back
> in sync with the logical relname.)

At least on UNIX, couldn't you use a hard-link and change the name in
pg_class immediately? Let the brain-dead operating systems use the
vacuum method.


pgsql-hackers by date:

Previous
From: Lamar Owen
Date:
Subject: Re: Mandrake RPMS, was "Building PostgreSQL 7.0.1 documentation"
Next
From: Tom Lane
Date:
Subject: Re: OK, OK, Hiroshi's right: use a seperately-generated filename