| From: | Michal Kozusznik <kozusznik(dot)michal(at)ifortuna(dot)cz> | 
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> | 
| Cc: | <pgadmin-support(at)postgresql(dot)org> | 
| Subject: | Re: create (or replace) language | 
| Date: | 2012-06-18 15:21:34 | 
| Message-ID: | 4FDF477E.10103@ifortuna.cz | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgadmin-support | 
Yes, I should know it. thank you.
There are a few sentences about pg_dump syntax compatibility from 
postgresql documentation:
Because pg_dump is used to transfer data to newer versions of 
PostgreSQL, the output of pg_dump can be expected to load into 
PostgreSQL server versions newer than pg_dump's version. pg_dump can 
also dump from PostgreSQL servers older than its own version. 
(Currently, servers back to version 7.0 are supported.) However, pg_dump 
cannot dump from PostgreSQL servers newer than its own major version; it 
will refuse to even try, rather than risk making an invalid dump. Also, 
it is not guaranteed that pg_dump's output can be loaded into a server 
of an older major version — not even if the dump was taken from a server 
of that version. Loading a dump file into an older server may require 
manual editing of the dump file to remove syntax not understood by the 
older server.
>
> pgAdmin doesn't create the dump file - it just calls pg_dump. Make 
> sure you have the correct version of pg_dump in the directory pointed 
> to by the PG Bin Path setting on File -> Options dialog.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2012-06-19 13:38:07 | Re: RI_ConstraintTrigger | 
| Previous Message | Dave Page | 2012-06-18 15:18:10 | Re: create (or replace) language |