Re: Long running update - Mailing list pgsql-general

From Tom Lane
Subject Re: Long running update
Date
Msg-id 1880.1123822382@sss.pgh.pa.us
Whole thread Raw
In response to Re: Long running update  (Greg Stark <gsstark@mit.edu>)
Responses Re: Long running update  (Greg Stark <gsstark@mit.edu>)
List pgsql-general
Greg Stark <gsstark@mit.edu> writes:
> One feature that would be handy for doing this would be if Postgres supported
> READ DIRTY. Few databases support it, and Postgres currently doesn't, but it
> would be extremely handy for peeking to see how much progress an update,
> delete, or insert has made.

Would it?  My first thought on reading the OP was to recommend
contrib/pgstattuple, but I refrained after thinking that if the table
is all that big, the last thing you need is someone doing a seqscan of
the whole table to see where you are.  Much less doing so repeatedly.

            regards, tom lane

pgsql-general by date:

Previous
From: Tomek Grzejszczyk
Date:
Subject: Re: function accepting a row
Next
From: Martijn van Oosterhout
Date:
Subject: Re: plphp crashing server