It's my bad.
Has to do with the sequence having the default value and *NOT* having
been called.
See -patches for update to simply skip START WITH in that case.
On Tue, 2003-03-25 at 10:08, Bruce Momjian wrote:
> I just did 'CREATE SEQUENCE x' and pg_dump produced:
>
> CREATE SEQUENCE x
>
>Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Patch applied. Thanks.
>
> Did you do anything to address my complaints about this patch?
Yes. It is a new version of the patch, with comments in each section.
I am attaching the patch --- any other changes?
--
Bruce Momjian
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Patch applied. Thanks.
Did you do anything to address my complaints about this patch?
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists at once with the
Stephan Szabo <[EMAIL PROTECTED]> writes:
> That's because the set default uses a pretty ugly hack. It plans the
> query with =NULL and then replaces the NULL with the default value's
> stored plan info. My first guess is that it's something with this that's
> causing the crash.
I've applied the
Patch applied. Thanks.
---
Laurent FAILLIE wrote:
> Hello Bruce,
>
> there is a contextual diff of my patch w/ the current
> (I hope) snapshot of postgresql.
>
> I test it on my own database, but I found another bug
> w/
Stephan Szabo <[EMAIL PROTECTED]> writes:
> Either way works for me. :) I'd guess it should look more like the default
> inserting stuff in copy for getting the expression's value. Doesn't look
> too hard to change (might take me a couple of days due to work, but I
> don't think that'll be a big i
On Thu, 27 Mar 2003, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> > That's because the set default uses a pretty ugly hack. It plans the
> > query with =NULL and then replaces the NULL with the default value's
> > stored plan info. My first guess is that it's something with thi
Stephan Szabo <[EMAIL PROTECTED]> writes:
> That's because the set default uses a pretty ugly hack. It plans the
> query with =NULL and then replaces the NULL with the default value's
> stored plan info. My first guess is that it's something with this that's
> causing the crash.
Yeah, it's faili
A. Hackmann ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
PANIC: open of /scratch/production_2/pg_clog/0996 failed: No such file or directory
Long Description
Hi,
I'm loading aprrox. 20GB into a Postgresql 7.3.2 db (using COP
