the transaction is visible to other sessions before
the slave ACKs.
Yes, their docs are not clear on this.
--
Mark Callaghan
mdcal...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
is vague.
It is great if Postgres doesn't have this issue. It wasn't clear to me
from lurking on this list. I hope your docs highlight the behavior as
not having the issue is a big deal.
--
Mark Callaghan
mdcal...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
creating replication lag between the primary and standby servers. I
also provided the text for that
(http://bugs.mysql.com/bug.php?id=57911) if you are concerned about
copying.
--
Mark Callaghan
mdcal...@gmail.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
assume that the behavior with covering indexes but
without index-only scans is similar to not having index-only scans.
I collect 95th percentile response times for my popular queries and
they are much improved with the use of covering indexes.
--
Mark Callaghan
mdcal...@gmail.com
--
Sent via pgsql
