On Friday, November 13, 2015 3:41 PM, Jim Nasby
wrote:
> On 11/10/15 3:42 PM, Jason Jho wrote:
>> We using Postgres 9.3.10
>> What is the most confusing part in all of this is why a DROP
>> SCHEMA CASCADE and a fresh pg_restore would somehow fix the
>> problem. Even a fresh reboot didn't fix it
On 11/10/15 3:42 PM, Jason Jho wrote:
On one particular day, this query hung for many hours and even while we
killed pids for running queries and any locks granted, the query would
never return. Also no hints of blocking processes. After some digging
through some I/O metrics, we didn't see any
Hi,
We using Postgres 9.3.10 on Amazon RDS and running into some strange
behavior that has been tough to track down and debug (partially due to the
limited admin access from RDS).
We're running a read-only query that normally takes ~10-15 min., but also
runs concurrently with several other intens
[EMAIL PROTECTED] writes:
> We have to inserts a records(15000- 2) into a table which also
> contains (15000-2) records, then after insertion, we have to delete
> the records according to a business rule.
> Above process is taking place in a transaction and we are using batches
> of 128 to
We have to inserts a records(15000- 2) into a table which also
contains (15000-2) records, then after insertion, we have to delete
the records according to a business rule.
Above process is taking place in a transaction and we are using batches
of 128 to insert records.
Everything works fi
