an update query.
>
> Thank you again!
> F
>
>
> Da: Melvin Davidson [melvin6...@gmail.com]
> Inviato: sabato 2 dicembre 2017 16.22
> A: Job
> Cc: pgsql-gene...@postgresql.org
> Oggetto: Re: Problems with triggers and table lock
>
> On Fri, Dec 1
[melvin6...@gmail.com]
Inviato: sabato 2 dicembre 2017 16.22
A: Job
Cc: pgsql-gene...@postgresql.org
Oggetto: Re: Problems with triggers and table lock
On Fri, Dec 1, 2017 at 4:39 PM, Job
mailto:j...@colliniconsulting.it>> wrote:
Dear guys,
we are using Postgresql 9.6.1 with Rubyrep in or
On Fri, Dec 1, 2017 at 4:39 PM, Job wrote:
> Dear guys,
>
> we are using Postgresql 9.6.1 with Rubyrep in order to replicate some
> tables across two different, and remote, database servers.
> Since few weeks sometimes when inserting/updating some rows, the statement
> remains waiting and table s
> On 1 Dec 2017, at 22:39, Job wrote:
>
> Dear guys,
>
> we are using Postgresql 9.6.1 with Rubyrep in order to replicate some tables
> across two different, and remote, database servers.
> Since few weeks sometimes when inserting/updating some rows, the statement
> remains waiting and table
Dear guys,
we are using Postgresql 9.6.1 with Rubyrep in order to replicate some tables
across two different, and remote, database servers.
Since few weeks sometimes when inserting/updating some rows, the statement
remains waiting and table seems locked for insert/updates.
When i issue "select
