On Wed, Aug 15, 2018 at 06:23:40PM -0400, Jonathan S. Katz wrote:
> This was added as an open item by Michael[1]. When the RMT discussed,
> we were able to make arguments both ways (i.e. adjusting the behavior vs.
> not).
>
> Peter, from your analysis it sounds like we should leave it, but I
> On Aug 10, 2018, at 4:39 AM, Peter Eisentraut
> wrote:
>
> On 09/08/2018 20:25, Vik Fearing wrote:
>> On 09/08/18 20:13, Peter Eisentraut wrote:
>>> On 09/08/2018 19:57, hubert depesz lubaczewski wrote:
I just noticed that when I called a procedure that commits and rollbacks
- the
On Thu, Aug 09, 2018 at 07:49:31PM +0200, hubert depesz lubaczewski wrote:
> I just noticed that when I called a procedure that commits and rollbacks
> - the xact_start in pg_stat_activity is not updated. Is it intentional?
>
> I'm on newest 12devel, built today.
That sounds incorrect to me. I
On 09/08/2018 20:25, Vik Fearing wrote:
> On 09/08/18 20:13, Peter Eisentraut wrote:
>> On 09/08/2018 19:57, hubert depesz lubaczewski wrote:
>>> I just noticed that when I called a procedure that commits and rollbacks
>>> - the xact_start in pg_stat_activity is not updated. Is it intentional?
>>
On 09/08/18 20:13, Peter Eisentraut wrote:
> On 09/08/2018 19:57, hubert depesz lubaczewski wrote:
>> I just noticed that when I called a procedure that commits and rollbacks
>> - the xact_start in pg_stat_activity is not updated. Is it intentional?
>
> It's an artifact of the way this is
On 09/08/2018 19:57, hubert depesz lubaczewski wrote:
> I just noticed that when I called a procedure that commits and rollbacks
> - the xact_start in pg_stat_activity is not updated. Is it intentional?
It's an artifact of the way this is computed. The reported transaction
timestamp is the
