Ken Tanzer writes:
> On Sat, Jul 20, 2019 at 12:25 PM Tom Lane wrote:
>> There's been assorted talk about various optimizations to
>> avoid unnecessary duplicate function calls,
> So I had read the sentence below to mean my functions would only get called
> once. But is that sentence only suppo
On Mon, Jul 22, 2019 at 1:42 AM Fabio Pardi wrote:
>
> Hello,
>
>
> I recently spent a bit of time benchmarking effective_io_concurrency on
> Postgres.
>
> I would like to share my findings with you:
>
> https://portavita.github.io/2019-07-19-PostgreSQL_effective_io_concurrency_benchmarked/
>
> C
On Sat, Jul 20, 2019 at 12:25 PM Tom Lane wrote:
> Ken Tanzer writes:
> > On Sat, Jul 20, 2019 at 7:46 AM Tom Lane wrote:
> >> and then to add insult to injury, has to search pg_description a second
> >> time for each hit.
>
> > Not sure if I'm understanding this correctly, but are you saying t
Hi Rick,
thanks for your inputs.
On 22/07/2019 14:06, Rick Otten wrote:
>
>
>
> You didn't mention what type of disk storage you are using, or if that
> matters.
I actually mentioned I m using SSD, in RAID 10. Also is mentioned I tested in a
no-RAID setup. Is that what you mean?
The num
On Mon, Jul 22, 2019 at 2:42 AM Fabio Pardi wrote:
> Hello,
>
>
> I recently spent a bit of time benchmarking effective_io_concurrency on
> Postgres.
>
> I would like to share my findings with you:
>
>
> https://portavita.github.io/2019-07-19-PostgreSQL_effective_io_concurrency_benchmarked/
>
> C
