Re: pgbench - allow to specify scale as a size

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Mark Wong <mark(at)2ndQuadrant(dot)com>
Cc: Alvaro Hernandez <aht(at)ongres(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgbench - allow to specify scale as a size
Date: 2018-02-20 10:06:26
Message-ID: alpine.DEB.2.20.1802201104480.6091@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

> Now the overhead is really 60-65%. Although the specification is unambiguous,
> but we still need some maths to know whether it fits in buffers or memory...
> The point of Karel regression is to take this into account.
> Also, whether this option would be more admissible to Tom is still an open
> question. Tom?

Here is a version with this approach: the documentation talks about
"actual data size, without overheads", and points out that storage
overheads are typically an additional 65%.


Attachment Content-Type Size
pgbench-scale-size-3.patch text/x-diff 7.8 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2018-02-20 10:10:15 Re: ALTER TABLE ADD COLUMN fast default
Previous Message Aleksander Alekseev 2018-02-20 09:52:53 Re: CURRENT OF causes an error when IndexOnlyScan is used