Re: New GUC to sample log queries - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: New GUC to sample log queries
Date
Msg-id 20180531132216.GA15397@paquier.xyz
Whole thread Raw
In response to Re: New GUC to sample log queries  (Adrien Nayrat <adrien.nayrat@anayrat.info>)
Responses Re: New GUC to sample log queries  (Adrien Nayrat <adrien.nayrat@anayrat.info>)
List 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.nayrat@anayrat.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.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: "REIX, Tony"
Date:
Subject: RE:PostgreSQL 11 beta1 on AIX 7.2 : 2 failures in 32bit mode
Next
From: Aleksander Alekseev
Date:
Subject: Re: [Proposal] Table-level Transparent Data Encryption (TDE) and KeyManagement Service (KMS)