| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Mitu Verma <mitu(dot)verma(at)ericsson(dot)com>, "'pgsql-general(at)postgresql(dot)org' (pgsql-general(at)postgresql(dot)org)" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: clearing of the transactions shown in pg_locks |
| Date: | 2015-04-29 22:47:14 |
| Message-ID: | 55415F72.7030604@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 4/29/15 12:32 AM, Mitu Verma wrote:
> This script first does the indexing then it deletes the entries from the
> table. Now issue is that this script is taking lot of time and has
> acquired some locks also. Nor sure if it is happening due to indexing or
> what.
Mixing DDL with bulk DML operations is not a recipe for good
concurrency. For that matter, running DDL on a recurring basis isn't
good either.
BTW, you might want to look at using PgQ to do the queuing; it has
different methods of maintaining it's queues so you don't run into these
sort of problems.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-04-29 22:50:55 | Re: newsfeed type query |
| Previous Message | Jim Nasby | 2015-04-29 22:43:19 | Re: Pg_bulkload and speed |