Re: Running update in chunks? - Mailing list pgsql-general

relid             | 26710
schemaname        | cars
relname           | imports
seq_scan          | 280
seq_tup_read      | 25873543
idx_scan          | 4
idx_tup_fetch     | 2749
n_tup_ins         | 98926
n_tup_upd         | 6350466
n_tup_del         | 92
n_tup_hot_upd     | 625286
n_live_tup        | 98834
n_dead_tup        | 0
last_vacuum       | 2013-01-25 21:55:36.078614+13
last_autovacuum   | 2013-01-25 21:58:40.850546+13
last_analyze      | 2013-01-25 21:55:36.305967+13
last_autoanalyze  | 2013-01-25 21:51:54.307639+13
vacuum_count      | 6
autovacuum_count  | 32
analyze_count     | 6
autoanalyze_count | 25


On Wed, Jan 23, 2013 at 7:50 AM, Steve Crawford
<scrawford@pinpointresearch.com> wrote:
> On 01/21/2013 05:02 PM, Tim Uckun wrote:
>>
>> I already posted the schema earlier. It's a handful of integer fields
>> with one hstore field.
>
>
> Oh well. I can't find it but maybe it got lost in shipping or eaten by a
> spam filter.
>
>
>>
>>
>> On Tue, Jan 22, 2013 at 1:23 PM, Steve Crawford
>> <scrawford@pinpointresearch.com> wrote:
>>>
>>> select * from pg_stat_user_tables where relname='yourtable';
>>
>>
>>
>> Messy output
>
> Don't know if you are in psql but if so, expanded display works for this.
> I.e.:
> steve@[local] => \x
> Expanded display is on.
> steve@[local] => select * from pg_stat_user_tables where relname='footest';
> -[ RECORD 1 ]-----+------------------------------
> relid             | 781691
> schemaname        | public
> relname           | footest
> seq_scan          | 3
> seq_tup_read      | 609
> idx_scan          |
> idx_tup_fetch     |
> n_tup_ins         | 609
> n_tup_upd         | 0
> n_tup_del         | 0
> n_tup_hot_upd     | 0
> n_live_tup        | 301
> n_dead_tup        | 0
> last_vacuum       |
> last_autovacuum   |
> last_analyze      |
> last_autoanalyze  | 2012-12-19 08:42:23.347368-08
> vacuum_count      | 0
> autovacuum_count  | 0
> analyze_count     | 0
> autoanalyze_count | 2
>
>
>
>>
>>
>>
"relid","schemaname","relname","seq_scan","seq_tup_read","idx_scan","idx_tup_fetch","n_tup_ins","n_tup_upd","n_tup_del","n_tup_hot_upd","n_live_tup","n_dead_tup","last_vacuum","last_autovacuum","last_analyze","last_autoanalyze","vacuum_count","autovacuum_count","analyze_count","autoanalyze_count"
>>
>> 26710,"chrysler","imports",274,25280539,4,2749,98926,5757462,92,327542,98834,0,"2013-01-22
>> 12:28:29.01505+13","2013-01-22 12:32:29.249588+13","2013-01-22
>> 12:28:29.173772+13","2013-01-22 12:32:44.123493+13",3,30,3,24
>>
>>
> So at least autovacuum is running (and some manual vacuum and analyze as
> well).
>
> Cheers,
> Steve
>


--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general