On 04/11/2015 17:53, Rob Sargent wrote:
On 11/04/2015 03:03 AM, Achilleas Mantzios wrote:
Sorry for being kind of late to the party (I was in 2015.PgConf.EU !!), and not
having read
most of the replies, what we have been successfully doing for this problem for
our app
is do it this way :
On Thursday, November 5, 2015 12:16 AM, Jiří Hlinka
wrote:
> My opinion is, that pg_repack should guarantee a consistent,
> deadlock-free behaviour via proper locking policy
I would be very interesting in seeing a description of what locking
policy would guarantee
On 11/05/2015 11:08 AM, Gavin Flower wrote:
On 06/11/15 04:33, Rob Sargent wrote:
On 11/05/2015 04:56 AM, Achilleas Mantzios wrote:
On 04/11/2015 17:53, Rob Sargent wrote:
On 11/04/2015 03:03 AM, Achilleas Mantzios wrote:
Sorry for being kind of late to the party (I was in 2015.PgConf.EU
Hi
I have been investigating a problem with one of our production databases
where every few weeks the database suddenly came to a grinding
halt. When this happened, queries needed much more time to complete and
just opening a local db connection with psql could take up to 30
seconds.
The
On 06/11/15 04:33, Rob Sargent wrote:
On 11/05/2015 04:56 AM, Achilleas Mantzios wrote:
On 04/11/2015 17:53, Rob Sargent wrote:
On 11/04/2015 03:03 AM, Achilleas Mantzios wrote:
Sorry for being kind of late to the party (I was in 2015.PgConf.EU
!!), and not having read
most of the replies,
On Thu, Nov 5, 2015 at 10:38 AM, Julian v. Bock wrote:
> After doing some debugging it seems that the backend processes are
> spending most of their time in spinlocks in TransactionIdIsInProgress()
> trying to get a lock on ProcArrayLock. This function is called more
> often
In PostgreSQL, there is no “DROP PRIMARY KEY”. Instead, you need to use
DROP INDEX index_name;
http://www.postgresql.org/docs/9.4/interactive/sql-dropindex.html
On Thu, Nov 5, 2015 at 10:52 PM, M Tarkeshwar Rao <
m.tarkeshwar@ericsson.com> wrote:
> Hi,
>
>
>
> one thing in oracle is there
Hi,
one thing in oracle is there any difference between "DROP PRIMARY KEY" used
directly in oracle to drop primary key, or "DROP CONSTRAINT CDRAUDITPOINT_pk",
as first syntax is not available in postgres and we need to give primary key
name as constraint to delete a key. SO right now to delete
On 11/05/2015 07:52 PM, M Tarkeshwar Rao wrote:
Hi,
one thing in oracle is there any difference between “DROP PRIMARY KEY”
used directly in oracle to drop primary key, or “DROP CONSTRAINT
CDRAUDITPOINT_pk”, as first syntax is not available in postgres and we
need to give primary key name as
Hi Kevin,
my point was, that pg_repack deadlocked itself - I think it should be
possible to guarantee deadlock-free behavior at least via advisory lock for
operations of pg_repack itself (I understand it is not possible to
guarantee this across more apps). If it is not true, I'd be glad to hear
On Fri, Nov 6, 2015 at 4:08 PM, Jiří Hlinka wrote:
> my point was, that pg_repack deadlocked itself - I think it should be
> possible to guarantee deadlock-free behavior at least via advisory lock for
> operations of pg_repack itself (I understand it is not possible to
M Tarkeshwar Rao schrieb am 06.11.2015 um 04:52:
> one thing in oracle is there any difference between “DROP PRIMARY
> KEY” used directly in oracle to drop primary key, or “DROP CONSTRAINT
> CDRAUDITPOINT_pk”, as first syntax is not available in postgres and
> we need to give primary key name as
On 11/05/2015 04:56 AM, Achilleas Mantzios wrote:
On 04/11/2015 17:53, Rob Sargent wrote:
On 11/04/2015 03:03 AM, Achilleas Mantzios wrote:
Sorry for being kind of late to the party (I was in 2015.PgConf.EU
!!), and not having read
most of the replies, what we have been successfully doing for
13 matches
Mail list logo