Hi list !
I have a quite large table with a PostGIS-geometry field (~25M rows)
representing road segments.
The segments are classified in 9 classes (from 0 to 8), based on their
importance.
I am trying some different methods for optimizing queries on this table.
I decided to try with a
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
[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
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 very
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)---
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
