From: Riccardo G. Facchini <abief_ag_-postgresql@yahoo.com>
To: abief_ag_-postgresql@yahoo.com
To: pgsql-sql@postgresql.org
Subject: Re: from PG_DUMP to CVS
Date: Thu, 26 Aug 2004 03:43:20 -0700 (PDT)
Message-ID: <20040826104320.60872.qmail@web13922.mail.yahoo.com> (raw)
In-Reply-To: <6.1.1.1.0.20040826202701.05c283e0@203.8.195.10>
--- Philip Warner <__> wrote:
> At 08:04 PM 26/08/2004, Riccardo G. Facchini wrote:
> >Does somebody know of a script that does this job?
>
> No, but a very useful idea.
>
> Sounds like another dump format to me -- so long as a well-defined
> structure that is likely to remain invariant over versions can be
> used. A
> client uses a trivial script to dump functions, but not tables,
> triggers or
> anything else.
>
> The simplest format might be to use the database names as a level 1
> dir,
> schema names at level 2, and entry names at level 3, then create
> files for
> the 'definition', 'data' etc.
>
> It would be a little confusing when ACLs and constraints were dumped
> (eg.
> they would not appear under the tables). But it would be consistent,
> at least.
>
> Of course it would be impossible to restore from such a beast since
> we
> would be throwing away ordering -- I think.
>
[..]
The plan is not to have something to be restored, but something that
can be published on a CVS server, in order to see what has been
modified overtime... I'd love to have this beast running daily.
If you know of something even similar to what I'm looking for, let me
know.
regards,
Riccardo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: abief_ag_-postgresql@yahoo.com
Subject: Re: from PG_DUMP to CVS
In-Reply-To: <20040826104320.60872.qmail@web13922.mail.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox