On 02/13/2017 11:50 AM, François Beaulieu wrote:
>
>> On Feb 13, 2017, at 1:56 PM, Adrian Klaver wrote:
>>
>> On 02/13/2017 09:04 AM, François Beaulieu wrote:
>>>
On Feb 13, 2017, at 11:45 AM, Adrian Klaver
wrote:
>>
> On Feb 13, 2017, at 1:56 PM, Adrian Klaver wrote:
>
> On 02/13/2017 09:04 AM, François Beaulieu wrote:
>>
>>> On Feb 13, 2017, at 11:45 AM, Adrian Klaver
>>> wrote:
>>>
>
On 02/13/2017 09:04 AM, François Beaulieu wrote:
On Feb 13, 2017, at 11:45 AM, Adrian Klaver wrote:
|
3) Are the first row and the second row in the same partition?
Doubtful, the problem
> On Feb 13, 2017, at 11:45 AM, Adrian Klaver wrote:
>
> On 02/13/2017 07:59 AM, François Beaulieu wrote:
>>
>>> On Feb 13, 2017, at 10:28 AM, Adrian Klaver
>>> wrote:
>>>
>>> On 02/10/2017 02:54 PM, François Beaulieu wrote:
On 02/13/2017 07:59 AM, François Beaulieu wrote:
On Feb 13, 2017, at 10:28 AM, Adrian Klaver wrote:
On 02/10/2017 02:54 PM, François Beaulieu wrote:
Hi all,
I’m trying to feed a worker process on another server using pg_notify in a
trigger. I’m running pgsql
> On Feb 13, 2017, at 10:28 AM, Adrian Klaver wrote:
>
> On 02/10/2017 02:54 PM, François Beaulieu wrote:
>>
>> Hi all,
>>
>> I’m trying to feed a worker process on another server using pg_notify in a
>> trigger. I’m running pgsql 9.4 and hitting some behaviour
On 02/10/2017 02:54 PM, François Beaulieu wrote:
Hi all,
I’m trying to feed a worker process on another server using pg_notify in a
trigger. I’m running pgsql 9.4 and hitting some behaviour that I’m hoping is
just a bug that can be solved with an upgrade, but I’m not finding any
references
Hi all,
I’m trying to feed a worker process on another server using pg_notify in a
trigger. I’m running pgsql 9.4 and hitting some behaviour that I’m hoping is
just a bug that can be solved with an upgrade, but I’m not finding any
references to it being a known bug and the uptime on my