Re: New GUC to sample log queries

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Adrien Nayrat <adrien(dot)nayrat(at)anayrat(dot)info>
Cc: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: New GUC to sample log queries
Date: 2018-05-31 13:22:16
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Thu, May 31, 2018 at 02:37:07PM +0200, Adrien Nayrat wrote:
> On 05/31/2018 03:34 AM, David Rowley wrote:
>> On 31 May 2018 at 06:44, Adrien Nayrat <adrien(dot)nayrat(at)anayrat(dot)info> wrote:
>>> Here is a naive SELECT only bench with a dataset which fit in ram (scale factor
>>> = 100) and PGDATA and log on a ramdisk:
>>> shared_buffers = 4GB
>>> seq_page_cost = random_page_cost = 1.0
>>> logging_collector = on (no rotation)
>> It would be better to just: SELECT 1; to try to get the true overhead
>> of the additional logging code.
> Right, I wonder why I didn't have the idea :)

Using prepared statements help also in reducing the load with
unnecessary planning.

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Aleksander Alekseev 2018-05-31 13:32:44 Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS)
Previous Message REIX, Tony 2018-05-31 13:20:05 RE:PostgreSQL 11 beta1 on AIX 7.2 : 2 failures in 32bit mode