Re: Re: Planning counters in pg_stat_statements (using pgss_store)

From: David Steele <david(at)pgmasters(dot)net>
To: legrand legrand <legrand_legrand(at)hotmail(dot)com>
Cc: Sergei Kornilov <sk(at)zsrv(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: Planning counters in pg_stat_statements (using pgss_store)
Date: 2019-03-20 10:43:03
Message-ID: 422d3baf-81d7-7292-91c5-50dd28cecfc8@pgmasters.net
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

Hi PAscal,

On 2/15/19 11:32 AM, Sergei Kornilov wrote:
> Hi
>
>>>  +#define PG_STAT_STATEMENTS_COLS_V1_4 25
>>
>> I thought it was needed when adding new columns, isn't it ?
>
> Yes, this is needed. I mean it should be PG_STAT_STATEMENTS_COLS_V1_8: because such change was made for 1.8 pg_stat_statements version. Same thing for other version-specific places.

This patch has been waiting for an update for over a month. Do you know
when you will have one ready? Should we move the release target to PG13?

Regards,
--
-David
david(at)pgmasters(dot)net

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fred .Flintstone 2019-03-20 10:43:24 Re: PostgreSQL pollutes the file system
Previous Message David Rowley 2019-03-20 10:41:53 Re: selecting from partitions and constraint exclusion