Re: pgbench doc fix - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: pgbench doc fix
Date
Msg-id alpine.DEB.2.21.1811302100450.19913@lancre
Whole thread Raw
In response to Re: pgbench doc fix  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: pgbench doc fix  (Tatsuo Ishii <ishii@sraoss.co.jp>)
List pgsql-hackers
>>>> So I do not think a more precise wording harms. Maybe: "prepared: use
>>>> extended query protocol with REUSED named prepared statements" would
>>>> be even less slightly ambiguous.
>>>
>>> I like this. But maybe we can remove "named"?
>>
>> I also think it makes sense to adjust wording a bit here, and this version
>> sounds good (taking into account the commentary about "named"). I'm moving this
>> to the next CF, where the question would be if anyone from commiters can agree
>> with this point.
>
> I don't see a concrete proposed patch here after the discussion.
>
> Reading the documentation again, we could go for much more detail here.
> For example, what's the point of having -M simple vs -M extended?

They do not use the same libpq-level approach (PQsendQuery vs 
PQsendQueryParams), so they are not exercising the same type of client? 
Pgbench is also about testing libpq performance.

-- 
Fabien.


pgsql-hackers by date:

Previous
From: Dmitry Dolgov
Date:
Subject: Re: Add function to release an allocated SQLDA
Next
From: Dmitry Dolgov
Date:
Subject: Re: Synchronous replay take III