Re: Why don't dumped files parse in pgAdmin3 query editor?

From: "Joris Dobbelsteen" <Joris(at)familiedobbelsteen(dot)nl>
To: <dlivesay(at)covad(dot)net>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: Why don't dumped files parse in pgAdmin3 query editor?
Date: 2007-03-05 15:43:45
Message-ID: 73427AD314CC364C8DF0FFF9C4D693FF0379B8@nehemiah.joris2k.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>-----Original Message-----
>From: pgsql-general-owner(at)postgresql(dot)org
>[mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of
>dlivesay(at)covad(dot)net
>Sent: maandag 5 maart 2007 16:28
>To: pgsql-general(at)postgresql(dot)org
>Subject: [GENERAL] Why don't dumped files parse in pgAdmin3
>query editor?
>
>Here's something I've always wondered. When you dump a
>database, the dumped file looks like ordinary SQL, but if I
>load it into a query editor window and try to execute it, I
>always get syntax errors. The specific errors vary, but it
>always makes it impossible to reload the data that way.
>
>In the past I've just used psql -f [file] [schema] to reload
>them, but I'm trying to do this on Windows, and I can't seem
>to get anything to work from the command shell, so I'm really stuck.

It seems it has some strange syntax that might be psql-specific, perhaps
its even for linux only.

However, it might make some difference if you dump with "Use insert
statements" instead of the normal copy from stdin. This seemed to work
for me last time. Your mileage may vary.

- Joris

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Angva 2007-03-05 15:48:17 Re: COPY FROM and multiple null strings
Previous Message Magnus Hagander 2007-03-05 15:39:25 Re: Why don't dumped files parse in pgAdmin3 query editor?