| From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
|---|---|
| To: | giuseppe petazzoni <giuseppe(dot)petazzoni(at)libero(dot)it> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #6091: Information |
| Date: | 2011-07-06 07:34:22 |
| Message-ID: | 4E140FFE.3090406@postnewspapers.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 6/07/2011 5:24 AM, giuseppe petazzoni wrote:
> I pg_dump .sql data and schema but is no compatible db2
> or mysql or informix or oracle
No, it won't be. Few if any SQL databases are fully compatible with each
other. In particular, the schema definitions (DDL) and type names tend
to vary wildly.
This is not a bug. The SQL standard doesn't define enough detail to make
sure that different databases are fully compatible with each other.
Note that pg_dump does have some options that help to make data dumps
(not the DDL) more compatible with other databasess. In particular, you
can tell it to use INSERT commands instead of COPY. See the
documentation for pg_dump for a detailed explaination.
If you want more help with your problem, try posting on pgsql-general
and explaining what you are trying to achieve. Include the error
message(s) you get, etc. See:
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
--
Craig Ringer
POST Newspapers
276 Onslow Rd, Shenton Park
Ph: 08 9381 3088 Fax: 08 9388 2258
ABN: 50 008 917 717
http://www.postnewspapers.com.au/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2011-07-06 11:02:56 | Re: R: Re: BUG #6091: Information |
| Previous Message | Tom Lane | 2011-07-06 00:06:11 | Re: BUG #6092: specific casting required for gist indexing of bigint |