On Thu, 2002-06-06 at 01:54, Sam Liddicott wrote:
> >
> > It would be interesting to see the 'vacuum full analyze'
> > results for the
> > system tables in that DB, although perhaps less interesting while you
> > are running your current solution - maybe a comparison would be
> > worthwhile.
>
Victor S ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
pg_dump don't works with 1500 tables
Long Description
pg_dump can't backup a database with 1500 tables. We have tried with all the options
and in two servers, one with p
Victor S ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
Error y bug about pg_dump and 1500 tables
Long Description
We have found the error. pg_dump works fine, sorry about the last bug.
Bye
Sample Code
No file was uploaded
Hi there,
this is rather uncritical, but there's a mistake in the Postgres
Reference Manual, concerning the COPY command:
http://www.postgresql.org/users-lounge/docs/7.1/reference/sql-copy.html
During the notes paragraph, 'COPY TO' and 'COPY FROM' are confused a few
times, e.g. in the sentences
I don't know what syntax uses parens for stored procedure cursors, but
we don't support it. Place the '1' in the cursor WHERE clause. You
can't pass it into the cursor using parens.
---
[EMAIL PROTECTED] wrote:
> Eduardo
