Re: Patch for BUG #2073: Can't drop sequence when created

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: Dhanaraj M <Dhanaraj(dot)M(at)Sun(dot)COM>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Patch for BUG #2073: Can't drop sequence when created
Date: 2006-04-30 01:09:19
Message-ID: 200604300109.k3U19Jk14225@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Tom Lane wrote:
> I wrote:
> > Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >> Patch applied. Thanks.
>
> > Has this been reviewed at all? I thought we were still discussing what
> > the behavior should be, let alone whether the patch is correct.
>
> Actually, now that I look at it, this patch is definitely *not* correct,
> as it does not implement any of the behaviors suggested as reasonable;
> and the discussion is still ongoing in any case.
>
> Please revert.

Done.

--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2006-04-30 02:09:38 Re: Patch for %Allow per-database permissions to be set via
Previous Message Tom Lane 2006-04-30 00:24:59 Re: [BUGS] BUG #2401: spinlocks not available on amd64