C comments: remove odd blank lines after #ifdef WIN32 lines
A few more
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/242c2737fbec05a756e516f6e2fec4b739cc49d1
Modified Files
--
src/backend/utils/mb/mbutils.c |1 -
src/bin/initdb/initdb.c
C comments: remove odd blank lines after #ifdef WIN32 lines
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/886c0be3f65bdbb68e86ec2d66a8c1a4c34b2923
Modified Files
--
src/backend/access/transam/xlog.c |1 -
src/backend/libpq/pqcomm.c |1
On 12 March 2014 21:30, Heikki Linnakangas wrote:
> Only WAL-log the modified portion in an UPDATE, if possible.
>
> When a row is updated, and the new tuple version is put on the same page as
> the old one, only WAL-log the part of the new tuple that's not identical to
> the old. This saves signi
Only WAL-log the modified portion in an UPDATE, if possible.
When a row is updated, and the new tuple version is put on the same page as
the old one, only WAL-log the part of the new tuple that's not identical to
the old. This saves significantly on the amount of WAL that needs to be
written, in t
Items on GIN data pages are no longer always 6 bytes; update gincostestimate.
Also improve the comments a bit.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/17d787a3b160eefb2ff4a3fdf12ca1fedc02cbc1
Modified Files
--
src/backend/utils/adt/selfuncs.c |
Show PIDs of lock holders and waiters in log_lock_waits log message.
Christian Kruse, reviewed by Kumar Rajeev Rastogi.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/588fb5071545ce6e8ffb6a88e146789560e6c879
Modified Files
--
doc/src/sgml/sources.sgml
test_decoding: Documentation fix.
Andres Freund
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/a0b4c355c2f4e26735d28372c49f4661621988f2
Modified Files
--
doc/src/sgml/test-decoding.sgml |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Sent
Fix incorrect assertion about historical snapshots.
Also fix some nearby comments.
Andres Freund
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/336a578b8c8866490e0d9069f10c17ba14f4705a
Modified Files
--
src/backend/utils/time/snapmgr.c | 10 ++---
Comment fixes related to logical decoding.
Andres Freund, per complaints by Peter Eisentraut.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/890194f14d6ff6838d79215b8ba62786185aa9a2
Modified Files
--
contrib/test_decoding/test_decoding.c |2 +-
s
Allow opclasses to provide tri-valued GIN consistent functions.
With the GIN "fast scan" feature, GIN can skip items without fetching all
the keys for them, if it can prove that they don't match regardless of
those keys. So far, it has done the proving by calling the boolean
consistent function wi
In WAL replay, restore GIN metapage unconditionally to avoid torn page.
We don't take a full-page image of the GIN metapage; instead, the WAL record
contains all the information required to reconstruct it from scratch. But
to avoid torn page hazards, we must re-initialize it from the WAL record
ev
In WAL replay, restore GIN metapage unconditionally to avoid torn page.
We don't take a full-page image of the GIN metapage; instead, the WAL record
contains all the information required to reconstruct it from scratch. But
to avoid torn page hazards, we must re-initialize it from the WAL record
ev
In WAL replay, restore GIN metapage unconditionally to avoid torn page.
We don't take a full-page image of the GIN metapage; instead, the WAL record
contains all the information required to reconstruct it from scratch. But
to avoid torn page hazards, we must re-initialize it from the WAL record
ev
In WAL replay, restore GIN metapage unconditionally to avoid torn page.
We don't take a full-page image of the GIN metapage; instead, the WAL record
contains all the information required to reconstruct it from scratch. But
to avoid torn page hazards, we must re-initialize it from the WAL record
ev
In WAL replay, restore GIN metapage unconditionally to avoid torn page.
We don't take a full-page image of the GIN metapage; instead, the WAL record
contains all the information required to reconstruct it from scratch. But
to avoid torn page hazards, we must re-initialize it from the WAL record
ev
In WAL replay, restore GIN metapage unconditionally to avoid torn page.
We don't take a full-page image of the GIN metapage; instead, the WAL record
contains all the information required to reconstruct it from scratch. But
to avoid torn page hazards, we must re-initialize it from the WAL record
ev
16 matches
Mail list logo
