| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Roman Neuhauser <neuhauser(at)sigpipe(dot)cz>, Akash Garg <akash(dot)garg(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Long running update |
| Date: | 2005-08-12 04:53:02 |
| Message-ID: | 1880.1123822382@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Greg Stark <gsstark(at)mit(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | srikanthutpala | 2005-08-12 04:54:08 | Re: getting information of tables and indexes |
| Previous Message | Tomek Grzejszczyk | 2005-08-12 04:50:50 | Re: function accepting a row |