| From: | Francisco Reyes <lists(at)stringsutils(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Select max(primary_key) taking a long time |
| Date: | 2010-05-22 23:22:55 |
| Message-ID: | cone.1274570575.501300.30938.1000@shelca |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Merlin Moncure writes:
> do a big delete recently? any other open transactions?
Some inserts were taking place. Roughly 2 to 5 million rows inside
transactions. We were doing some ETL and each batch represented a file we
were loading. We need to have the entire file or roll back so each file is
done within a transaction.
> the remedy for the former is to simply eat it (one time penalty) or
> rebuild the table. for the latter you simply have to resolve the
> other transaction.
I think it is related to the inserts... after they were done everything was
back to normal.
> how big is your table according to pg_relation_size()?
\dt+ is easier. :-)
116GB
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ivan Voras | 2010-05-23 02:40:20 | Full text search on a complex schema - a classic problem? |
| Previous Message | Merlin Moncure | 2010-05-22 17:05:38 | Re: Alter column position |