Re: Enhancement to pg_dump - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: Enhancement to pg_dump
Date
Msg-id 87r64zr08q.fsf@oxford.xeocode.com
Whole thread Raw
In response to Enhancement to pg_dump  ("Rob Kirkbride" <rob.kirkbride@gmail.com>)
Responses Re: Enhancement to pg_dump  ("Rob Kirkbride" <rob.kirkbride@gmail.com>)
List pgsql-hackers
"Rob Kirkbride" <rob.kirkbride@gmail.com> writes:

> Once I'm happy with it (I'm a bit rusty at C!), do I post the patch here?

I would say you should post *before* you have a patch you're happy with. As
soon as you have a specific plan of what you want to do it's best to post an
outline of it. That way you at least have a chance of avoiding wasting work in
the wrong direction.

Sometimes things don't really work out that way -- sometimes the plan sounds
good and it only becomes apparent there's a better way later -- but you're
best off getting the best chance you can.

Incidentally, I don't know exactly what the use case you're trying to cover
here is but you should consider looking at TRUNCATE instead of DELETE if
you're really deleting all the records in the table and can accept locking the
table.

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com Ask me about EnterpriseDB's Slony Replication
support!


pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: blatantly a bug in the documentation
Next
From: Stephen Frost
Date:
Subject: Re: WIP: Column-level Privileges