Tom Lane wrote:
> Scott Reed writes:
> > Would you accept the second part of that post about handling the file
> > name in pgAdmin Backup and Restore? I will resubmit if you think it
> > would be useful.
>
> You'd need to bug the pgAdmin folks about that; that's a separate
> project with its o
Scott Reed writes:
> Would you accept the second part of that post about handling the file
> name in pgAdmin Backup and Restore? I will resubmit if you think it
> would be useful.
You'd need to bug the pgAdmin folks about that; that's a separate
project with its own mailing lists.
Tom,
My apologies for wasting your time. I wasn't calling pg_restore as I'd
described but with the -f flag so of course it was hanging waiting for
input. I hope my embarrassment is sufficient punishment.
Would you accept the second part of that post about handling the file
name in pgAdmin Backu
"Scott Reed" writes:
> "pg_restore " hangs if the file format is not one of the
> non-plain-text formats created by pg_dump.
When I try to reproduce this I get
pg_restore: [archiver] input file does not appear to be a valid archive
Perhaps there are specific cases where it gets confused, but you
The following bug has been logged online:
Bug reference: 4699
Logged by: Scott Reed
Email address: sr...@avacoda.com
PostgreSQL version: 8.3
Operating system: Windows XP
Description:pg_restore hangs with incorrect file format
Details:
"pg_restore " hangs if the file
"Yuri Cherio" writes:
> psql -f "filename.sql" > "out_file_name"
> One would expect that standard output should not be accumulated until it
> blows up but instead would behave as a stream.
This is not the case, for various reasons that I don't feel like
debating right now. You might try using \
The following bug has been logged online:
Bug reference: 4698
Logged by: Yuri Cherio
Email address: y...@aergo.com
PostgreSQL version: 8.3.5-2
Operating system: Windows XP Pro, SP3
Description:psql.exe is exits reporting "out of memory" error
Details:
I have SELECT
When the parser sees the "@", it goes into "email state". In email
state, it recurses, trying to find out if the string after the "@" is a
valid hostname. That in turn goes into email state, recurses again and
so forth, until you reach the end of the string. Then, the recursion
unwinds back to
