From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Robins Tharakan <tharakan(at)gmail(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Pgbench with -f and -S |
Date: | 2016-04-17 15:54:11 |
Message-ID: | alpine.DEB.2.10.1604171734190.23313@sto |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Pgbench allows -f and -S combinations together where the doc says that -S
> effectively uses the internal select-only script.
>
> Is it okay to assume that -f is disregarded here? Or are they run in
> round-robin fashion (although then, how does it know which read-only part
> of my script to run?) or something else like that?
>
> Effectively, I think it should raise NOTICE that -f is useless here.
For the future 9.6, scripts options are cumulatives, so -f & -S can be
combined.
Indeed, for the <= 9.5 it seems that some options are silently ignores,
when combining -S/-f, only the last one is kept, it should be warned
about.
--
Fabien.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-04-17 16:01:48 | Re: pgsql: Allow Pin/UnpinBuffer to operate in a lockfree manner. |
Previous Message | David Steele | 2016-04-17 15:46:42 | Re: [HACKERS] Re: pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold < |