> We clearly need to have a 7.3.2, but I was thinking late January would
> be about the right time frame. Bugs are still trickling in (eg, the
> plpgsql one Neil just identified), and so far we've not seen anything
> that would make me feel we need an immediate release ...
I'm biased, but I think
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Are we near needing 7.3.2?
We clearly need to have a 7.3.2, but I was thinking late January would
be about the right time frame. Bugs are still trickling in (eg, the
plpgsql one Neil just identified), and so far we've not seen anything
that would make m
Are we near needing 7.3.2? The contraint dump patch is post-7.3.1 too,
and Tom applied a big fix recently to 7.3.X.
---
Laurette Cisneros wrote:
> That did the trick...fixed pg_dump!
>
> And, pg_restore works on it too!
That did the trick...fixed pg_dump!
And, pg_restore works on it too!
Yay, I can go home now.
Thanks very much for your help!
On Fri, 10 Jan 2003, Tom Lane wrote:
> Laurette Cisneros <[EMAIL PROTECTED]> writes:
> > This does not:
> > pg_dump -h myhost -p 5432 -Fc -f mydb.cpgdmp mydb
> > Segmen
Thanks.
I've nulled all the "comment on view"s but still get it...
On Fri, 10 Jan 2003, Tom Lane wrote:
> Laurette Cisneros <[EMAIL PROTECTED]> writes:
> > This does not:
> > pg_dump -h myhost -p 5432 -Fc -f mydb.cpgdmp mydb
> > Segmentation fault (core dumped)
>
> If you have any comments on
Laurette Cisneros <[EMAIL PROTECTED]> writes:
> This does not:
> pg_dump -h myhost -p 5432 -Fc -f mydb.cpgdmp mydb
> Segmentation fault (core dumped)
If you have any comments on views, this is probably an instance of a
known bug:
2002-12-27 12:10 tgl
* src/bin/pg_dump/: pg_dump.c (REL7_
Oh goodness it's even worse as pg_restore can't read the archive from the
first pg_dump:
pg_dump -h myhost -p 5432 -f mydb.pgdmp mydb
pg_restore -l mydb.pgdmp
pg_restore: [archiver] input file does not appear to be a valid archive
Thanks,
L.
On Fri, 10 Jan 2003, Laurette Cisneros wrote:
>
>
