libpq: Small code clarification, and avoid casting away const
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/e685a8e6651b0e55996e6eba6917302607866793
Modified Files
--
src/interfaces/libpq/fe-auth.c | 14 --
1 files changed, 8 insertions(+),
Add a hook for processing messages due to be sent to the server log.
Use-cases for this include custom log filtering rules and custom log
message transmission mechanisms (for instance, lossy log message
collection, which has been discussed several times recently).
As is our common practice for ho
Typo fix.
Fujii Masao
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/bc97c38115ed48c1dd27e9d534faae204427f9a5
Modified Files
--
src/backend/access/transam/xlog.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
--
Sent via pgsql-committers
Make the comments more clear on the fact that UpdateFullPageWrites() is not
safe to call concurrently from multiple processes.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/e587e2e3e39ec54772905b8e0ac7155a03253934
Modified Files
--
src/backend/access/tr
Simplify the way changes to full_page_writes are logged.
It's harmless to do full page writes even when not strictly necessary, so
when turning full_page_writes on, we can set the global flag first, and then
call XLogInsert. Likewise, when turning it off, we can write the WAL record
first, and the
Remove extra copies of LogwrtResult.
This simplifies the code a little bit. The new rule is that to update
XLogCtl->LogwrtResult, you must hold both WALWriteLock and info_lck, whereas
before we had two copies, one that was protected by WALWriteLock and another
protected by info_lck. The code that
