Dave Page a écrit :
Arnaud Lesauvage wrote:
Dave Page a écrit :
What does
C:\Program Files\pgAdmin III\1.6\pg_dump.exe --version
return?
"C:\Program Files\pgAdmin III\1.6\pg_dump.exe" --version
"pg_dump (PostgreSQL) 8.3devel"
No - please replace it with one from an 8.2 installation.
R
Arnaud Lesauvage wrote:
> Dave Page a écrit :
>> What does
>>
>> C:\Program Files\pgAdmin III\1.6\pg_dump.exe --version
>>
>> return?
>
>> "C:\Program Files\pgAdmin III\1.6\pg_dump.exe" --version
> "pg_dump (PostgreSQL) 8.3devel"
No - please replace it with one from an 8.2 installation.
Regards,
Dave Page a écrit :
What does
C:\Program Files\pgAdmin III\1.6\pg_dump.exe --version
return?
"C:\Program Files\pgAdmin III\1.6\pg_dump.exe" --version
"pg_dump (PostgreSQL) 8.3devel"
Is that correct ?
Regards
--
Arnaud
---(end of broadcast)-
Arnaud Lesauvage wrote:
Dave Page a écrit :
Are you sure you're running 1.6.3? I get (not the non default schema,
and that both the schema and table names need quoting):
C:\Program Files\PostgreSQL\8.2\bin\pg_dump.exe -i -h localhost -p
5432 -U postgres -F c -v -f "c:\foo.bak" -t "\"FOO\".\"R
Dave Page a écrit :
Are you sure you're running 1.6.3? I get (not the non default schema,
and that both the schema and table names need quoting):
C:\Program Files\PostgreSQL\8.2\bin\pg_dump.exe -i -h localhost -p 5432
-U postgres -F c -v -f "c:\foo.bak" -t "\"FOO\".\"Role\"" postgres
That's
Thanks.
Double quoting as suggested solves the problem and all seems to be working
as i expected. In particular i wasn't quoting the schema name, rather i
quoted the combined . string.
Regards, Simon
On 17/04/07, Dave Page <[EMAIL PROTECTED]> wrote:
Arnaud Lesauvage wrote:
> [EMAIL PROTECTED]
Arnaud Lesauvage wrote:
[EMAIL PROTECTED] a écrit :
I second this bug - i'm experiencing the same problem trying to backup
(dump) tables with mixed case names (e.g. MyTableName). I've installed
pgAdmin v1.6.3 and attempted to backup (compressed and plain, within
pgadmin, from cmd line) some tabl
[EMAIL PROTECTED] a écrit :
On Apr 16, 8:49 am, [EMAIL PROTECTED] (Arnaud Lesauvage)
wrote:
I found this bug already mentionned in the archives of January 2007, but it was
supposed to be fixed in 1.6.3.
Obviously it is not so, since I still have the error "No matching tables were
found" when t
On Apr 16, 8:49 am, [EMAIL PROTECTED] (Arnaud Lesauvage)
wrote:
> Hi list !
>
> I found this bug already mentionned in the archives of January 2007, but it
> was supposed to be fixed in 1.6.3.
> Obviously it is not so, since I still have the error "No matching tables were
> found" when trying to
Hi list !
I found this bug already mentionned in the archives of January 2007, but it was
supposed to be fixed in 1.6.3.
Obviously it is not so, since I still have the error "No matching tables were
found" when trying to perform a single table backup/
Dave Page wrote :
The command currently g
I run an ecommerce system on a webserver, which I want to move to a
different machine.
However, I am stalled because pg_dump fails with the following error:
pg_dump: ERROR: timestamp out of range
pg_dump: SQL command to dump the contents of table "server_hit_bin"
failed: PQendcop
ROTECTED]:
[pgadmin-support] pg_dump fails
Pg_dump fails with the following two
errors
unrecognized variable
client-encoding
and
ERROR: Attribute 'inhrel' not
found
database works fine, but cannot be backed
up
any ideas?
dvv
Pg_dump fails with the following two
errors
unrecognized variable client-encoding
and
ERROR: Attribute 'inhrel' not
found
database works fine, but cannot be backed
up
any ideas?
dvv
13 matches
Mail list logo
