On 06.07.2022 20:11, Robert Haas wrote:
On Thu, Mar 31, 2022 at 12:00 PM Julien Rouhaud wrote:
Indeed. Then there is a very simple solution for this particular case as
wal_records counter may only sometime becomes greater but never less.
The corresponding patch is attached.
+1 for this app
On Thu, Mar 31, 2022 at 12:00 PM Julien Rouhaud wrote:
> > Indeed. Then there is a very simple solution for this particular case as
> > wal_records counter may only sometime becomes greater but never less.
> > The corresponding patch is attached.
>
> +1 for this approach, and the patch looks good
Hi,
On Thu, Mar 31, 2022 at 06:08:01PM +0300, Anton A. Melnikov wrote:
> Hello!
>
> On 30.03.2022 22:36, Robert Haas wrote:
> > I don't think that the idea of "extra" WAL records is very principled.
> > It's pretty vague what "extra" means, and your definition seems to be
> > basically "whatever
Hello!
On 30.03.2022 22:36, Robert Haas wrote:
I don't think that the idea of "extra" WAL records is very principled.
It's pretty vague what "extra" means, and your definition seems to be
basically "whatever would be needed to make this test case pass." I
think the problem is basically with the
On Wed, Mar 30, 2022 at 2:20 AM Anton A. Melnikov wrote:
> > Can the test failures be encountered without such an elaborate setup? If
> > not,
> > then I don't really see why we need to do anything here?
>
> There was a real bug report from our test department. They do long time
> repetitive test
Hello,
thank you much for your attention and for your thought.
On 20.03.2022 20:36, Andres Freund wrote:
This patch introduces an additional counter of wal records not related to
the query being executed.
They're not unrelated though.
Yes, i've missformulated here.
Indeed there is a relatio
Hi,
On 2022-01-14 11:11:07 +0300, Anton A. Melnikov wrote:
> This patch introduces an additional counter of wal records not related to
> the query being executed.
They're not unrelated though.
> Due to this counter pg_stat_statement finds out the number of wal records
> that are not relevant to
Hello!
Here is the second version of the patch rebased onto the current master.
No logical changes.
All other attached files from previous letter are actual.
With best regards,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Companycommit 04ce779eb2
