From: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | "Bruce Momjian" <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | "PostgreSQL-development" <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | RE: [HACKERS] tables > 1 gig |
Date: | 1999-06-18 03:11:04 |
Message-ID: | 000e01beb938$335b9660$2801007e@cadzone.tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: Bruce Momjian [mailto:maillist(at)candle(dot)pha(dot)pa(dot)us]
> Sent: Friday, June 18, 1999 11:31 AM
> To: Hiroshi Inoue
> Cc: PostgreSQL-development
> Subject: Re: [HACKERS] tables > 1 gig
>
>
> > Unlinking unused segments after truncating to zero length may cause
> > the result such as
> >
> > Existent backends write to the truncated file to extend
> the relation
> > while new backends create a new segment file to extend the
> relation.
>
> How about my idea of creating a truncated file, the renaming it to the
> table file. That keeps the table open for other open file descriptors,
> but put a zero-length file in place in an atomic manner.
>
Sorry,I couldn't understand what you mean.
What is differenct from truncating existent files to zero length ?
Regards.
Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1999-06-18 03:15:32 | Re: [HACKERS] tables > 1 gig |
Previous Message | Billy G. Allie | 1999-06-18 02:55:32 | Re: [HACKERS] Re: UnixWare |