From: | J French <hikenboots(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Douglas McNaught <doug(at)mcnaught(dot)org>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Generating an ANSI compliant schema recreation script |
Date: | 2005-10-30 00:54:01 |
Message-ID: | 35b7725f0510291754v512ad017tb231138cd2d8e4ba@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
No problems. I am about to write a python script to cleanup the output of
pg_dump. Before I do I just wanted to verify that there wasn't an already
available script which I could feed directly into another ansi compliant
database without modification. No sense reinventing the wheel. The output of
pg_dump is pretty clean for this purpose already. just thought I'd ask
beforehand.
On 10/29/05, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> J French <hikenboots(at)gmail(dot)com> writes:
> > I did read the page. Been there done that, ran the script. My question
> was
> > if there was a canned script out there that I didn't have to clean up on
> the
> > fly. This will be an cron job for a convoluted development process.
>
> If your schema isn't using any non-standard features, I would think that
> the result of pg_dump would be pretty standard, with the exception of a
> few SET commands at the front and the ALTER OWNER commands. (The latter
> can be suppressed with --no-owner.) What exactly is giving you a
> problem?
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Crawford | 2005-10-30 03:20:34 | Re: Installation trouble -- oops |
Previous Message | Tom Lane | 2005-10-30 00:45:57 | Re: Generating an ANSI compliant schema recreation script |