Re: AW: Vacuum only with 20% old tuples

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
Cc: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: AW: Vacuum only with 20% old tuples
Date: 2000-07-25 10:41:12
Message-ID: 397D6EC8.D15A0FFD@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Zeugswetter Andreas SB wrote:

> > OK,I see. Your idea seems to be close to Vadim's *relink*.
> > However it isn't clear if *relink* has no problem.
> > In my test case on cygwin port ,*relink* doesn't work well.
> > *relink* caused an error if concurrent backends open the
> > *relink*ing table.
>
> All actions involving a rename of a file imho involve exclusive access
> to the table, thus no concurrent access is allowed/possible.
>

Once a table file was opened,it is not closed until the end of the
backend process except due to the shortage of file descriptors.

Even now,cygwin port has a flaw that we have no guarantee to
recreate a table safely after dropping the table. Unfortunately
we couldn't recreate the same named file until all processes
close the file in cygwin.

Regards.

Hiroshi Inoue

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas SB 2000-07-25 12:35:28 AW: AW: Vacuum only with 20% old tuples
Previous Message Zeugswetter Andreas SB 2000-07-25 10:16:50 AW: Vacuum only with 20% old tuples