Greg Smith <gsmith@gregsmith.com> writes:
> That clarifies the situation well enough for me. I think this is a two
> part problem then. It's not necessarily obvious that pgbench will use
> PGOPTIONS. In addition to that, the current documentation is less clear
> than it could be on the subject of what you can usefully put into
> PGOPTIONS. That's two small documentation patches I should be able to
> handle.
BTW, PGOPTIONS is actually just the environment-variable fallback for
the pgoptions argument to PQsetdbLogin() or the options=whatever
component of the conninfo string for PQconnectdb() --- it's the same
sort of animal as PGHOST or PGPORT. So those provide alternate paths
for getting at the same functionality, and any documentation patch
should be clear about this.
regards, tom lane
