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

From Tom Lane
Subject Re: OK, OK, Hiroshi's right: use a seperately-generated filename
Date
Msg-id 10206.961204349@sss.pgh.pa.us
Whole thread Raw
In response to Re: OK, OK, Hiroshi's right: use a seperately-generated filename  (Chris Bitmead <chris@bitmead.com>)
Responses Re: OK, OK, Hiroshi's right: use a seperately-generated filename  (The Hermit Hacker <scrappy@hub.org>)
List pgsql-hackers
Chris Bitmead <chris@bitmead.com> writes:
> 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.

Hmm ... maybe, but it doesn't seem worth the portability headache to
me.  We do have an NT port that we don't want to break, and I don't
think RENAME TABLE is worth the trouble of testing/supporting two
implementations.

Even on Unix, aren't there filesystems that don't do hard links?
Not that I'd recommend running Postgres on such a volume, but...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Chris Bitmead
Date:
Subject: Re: OK, OK, Hiroshi's right: use a seperately-generated filename
Next
From: "Hiroshi Inoue"
Date:
Subject: RE: OK, OK, Hiroshi's right: use a seperately-generated filename