On 16/01/15 14:37, Jim Nasby wrote:
On 1/15/15 7:12 PM, Fabio Ugo Venchiarutti wrote:
Greetings
Our company is writing a small ad-hoc implementation of a load
balancer for Postgres (`version()` = PostgreSQL 9.2.9 on
x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.4.7 20120313 (Red
Hat
ast_xlog_receive_location(),
pg_last_xlog_replay_location()
),
'000/'
)
;
--------
Thanks in advance
Fabio Ugo Venchiarutti
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
arguments then, as they're
inspected after the plan is cached?
Is dynamic SQL the recommended/only way around this?
Regards
Fabio Ugo Venchiarutti
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/
Greetings.
I'm in the process of indexing a virtual file system (on 9.2.9, build
info below) and I ran into what I perceive as an inconsistency in the
way index viability is assessed by the planner.
Perhaps I'm misinterpreting the docs, but it seems like stable functions
don't behave as per
