Gregory Stark wrote:
There is documentation
http://www.postgresql.org/docs/8.3/static/explicit-locking.html
However I found it very confusing when I was first learning. It's not really
the documentation's fault either, there are just a lot of different lock
levels with a lot of different combin
s?
Rob
2008/11/26 Gregory Stark <[EMAIL PROTECTED]>
> Rob Kirkbride <[EMAIL PROTECTED]> writes:
>
> > Richard,
> >
> > Yes, I've changed it use TRUNCATE rather than DELETE and it's working
> well for
> > us now.
>
> I'm a bit sur
ly be something we'll consider.
Rob
Richard Huxton wrote:
Rob Kirkbride wrote:
I've introduced a --delete-not-drop option which simply does a DELETE FROM %
rather than 'DROP and then CREATE'.
Beware foreign-keys slowing you - TRUNCATE all relevant tables shoul
n the table and therefore can continue.
I've introduced a --delete-not-drop option which simply does a DELETE FROM %
rather than 'DROP and then CREATE'.
I hope this sounds sensible and I haven't missed something - I'm still
learning!
Rob
2008/11/25 Gregory Stark <[EMAIL PROTE
Dave,
Ok thanks. Yes, we've got over 1/2 billion rows in one of our tables which
is interesting!
Will post back soon.
Rob
2008/11/25 Dave Page <[EMAIL PROTECTED]>
> On Tue, Nov 25, 2008 at 8:39 PM, Rob Kirkbride <[EMAIL PROTECTED]>
> wrote:
> > Hi,
> >
>
Hi,
I'm very new to hacking postgresql but am using on a very big site (
http://ojp.nationalrail.co.uk). One of the issues that we have is moving
data from a live database to a reports one. I've hacked an extra option to
pg_dump to delete from tables rather than dropping them.
Once I'm happy with
