Skip site navigation (1) Skip section navigation (2)

Re: Remove sort files

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Remove sort files
Date: 2001-05-23 19:46:34
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Anyway, I am still thinking about this.  I haven't addressed tables that
> > are orphaned by a rename aborting.
> >> 
> >> What makes you think that needs to be addressed?  We don't have that
> >> problem anymore AFAIK.
> > If one backend creates a new file for alter table, but crashes before
> > modifying pg_class, doesn't that file just hang around?
> ALTER TABLE doesn't create any new files.

What about CLUSTER?  If we do DROP COLUMN by creating a new heap, we
will use it then too, right?  Are those the only two that create new
files that could be orphaned?

Now that we have file numbers, seems we can do DROP COLUMN now reliably,

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to


pgsql-patches by date

Next:From: Tom LaneDate: 2001-05-23 19:57:47
Subject: Re: Remove sort files
Previous:From: Bruce MomjianDate: 2001-05-23 19:40:50
Subject: Re: Remove sort files

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group