| From: | Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Chris Bitmead <chris(at)bitmead(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: OK, OK, Hiroshi's right: use a seperately-generated filename |
| Date: | 2000-06-19 00:36:55 |
| Message-ID: | 394D6B27.DAAF60C8@nimrod.itg.telecom.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian wrote:
>
> > 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.
>
> Yes, we can hard-link, and let vacuum remove the old link.
BTW, how does vacuum know which files are obsolete. Does it just delete
files it doesn't know about?
What a good application for time travel!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ross J. Reedstrom | 2000-06-19 00:47:04 | Re: Big 7.1 open items |
| Previous Message | Hiroshi Inoue | 2000-06-19 00:24:56 | RE: OK, OK, Hiroshi's right: use a seperately-generated filename |