-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Given f1(x) as IMMUTABLE and f2(x) as IMMUTABLE, and f3(f1,f2) as
IMMUTABLE, does the query planner cache the result of f3 and reuse it
or if you want to get a little more speed you better explicitly define
yourself f3 as IMMUTABLE?
I had an aggregat
You may want to try Bucardo ... By performance, are you referring to latency?
If so, bandwidth between sites typically is the factor with latency in any
replication solution.
http://bucardo.org/
-Original Message-
From: pgsql-sql-ow...@postgresql.org [mailto:pgsql-sql-ow...@postgres
HELO
i am looking for strange things:
a timezone conversion AS transparent AS a charset encoding conversion are.
for __example__ (not intending to override the current behavior)
i want to see now()::timestampTZ always the same
(the server side time with the timezone predefined firmly)
and to s
On Fri, 2010-03-05 at 09:20 +0100, Iñigo Martinez Lasala wrote:
> For example, if you use functions or sentences that make use of
> timestamp, random, etc it won't be possible to use pg_pool since each
> node will have a different value.
> If not, it could probably work for you.
FWIW, timestamps