yes i did the soft upgrade (seems to work) but when doing
the pg_upgrade part it seems to no work... ok thanks for your advice.. i
will try.
so i came up with an idea and it seems to work just wanna make sure what you think?
- do a custom pg_dump of postgres 8.3.2+postgis 1.3
- do restore (with the perl script of postgis) within the postgres 9.2.4+postgis 2.0.4![]()
so i came up with an idea and it seems to work just wanna make sure what you think?
- do a custom pg_dump of postgres 8.3.2+postgis 1.3
- do restore (with the perl script of postgis) within the postgres 9.2.4+postgis 2.0.4
On Wed, Jul 3, 2013 at 7:12 PM, Sergey Konoplev <gray.ru@xxxxxxxxx> wrote:
On Mon, Jul 1, 2013 at 9:20 AM, Marcos Cano <mcano@xxxxxxxxx> wrote:Hm... have you performed soft upgrade to PostGIS 1.5.8?
> content of the file tables_using_names.txt:
> Database: dev
> public.geography_columns.f_table_schema
> public.geography_columns.f_table_name
> public.geography_columns.f_geography_column
If so then try to pg_dump the geography_columns table, then drop it,
do pg_upgrade, and restore the dump of geography_columns. It is just
my guess but it could help.
--
Kind regards,
Sergey Konoplev
PostgreSQL Consultant and DBA
Profile: http://www.linkedin.com/in/grayhemp
Phone: USA +1 (415) 867-9984, Russia +7 (901) 903-0499, +7 (988) 888-1979
Skype: gray-hemp
Jabber: gray.ru@xxxxxxxxx
