--On 23. Januar 2013 15:12:00 + Alvaro Herrera
wrote:
This patch introduces two additional lock modes for tuples: "SELECT FOR
KEY SHARE" and "SELECT FOR NO KEY UPDATE". These don't block each
other, in contrast with already existing "SELECT FOR SHARE" and "SELECT
FOR UPDATE". UPDATE c
Properly zero-pad the day-of-year part of the win32 build number
This ensure the version number increases over time. The first three digits
in the version number is still set to the actual PostgreSQL version
number, but the last one is intended to be an ever increasing build number,
which previosl
Properly zero-pad the day-of-year part of the win32 build number
This ensure the version number increases over time. The first three digits
in the version number is still set to the actual PostgreSQL version
number, but the last one is intended to be an ever increasing build number,
which previosl
Properly zero-pad the day-of-year part of the win32 build number
This ensure the version number increases over time. The first three digits
in the version number is still set to the actual PostgreSQL version
number, but the last one is intended to be an ever increasing build number,
which previosl
Properly zero-pad the day-of-year part of the win32 build number
This ensure the version number increases over time. The first three digits
in the version number is still set to the actual PostgreSQL version
number, but the last one is intended to be an ever increasing build number,
which previosl
Properly zero-pad the day-of-year part of the win32 build number
This ensure the version number increases over time. The first three digits
in the version number is still set to the actual PostgreSQL version
number, but the last one is intended to be an ever increasing build number,
which previosl
Properly zero-pad the day-of-year part of the win32 build number
This ensure the version number increases over time. The first three digits
in the version number is still set to the actual PostgreSQL version
number, but the last one is intended to be an ever increasing build number,
which previosl
Reject nonzero day fields in AT TIME ZONE INTERVAL functions.
It's not sensible for an interval that's used as a time zone value to be
larger than a day. When we changed the interval type to contain a separate
day field, check_timezone() was adjusted to reject nonzero day values, but
timetz_izone
Switch timelines if we crash soon after promotion.
Previous patch to skip checkpoints at end of recovery didn't
correctly perform crash recovery, fumbling the timeline switch.
Now we record the minRecoveryPointTLI of the newly selected
timeline, so that we crash recover to the correct timeline.
Bu
On 30 January 2013 17:26, Simon Riggs wrote:
>> Thanks for the test case, that was quick!
>
> OK, I can confirm this bug.
>
> This needs more work as is, so I'll revert and re-post.
The fix was pretty simple in the end, so I've not reverted, just
applied the fix.
If anyone really wants me to re
pg_upgrade docs: mention modification of postgresql.conf in new cluster
Mention it might be necessary to modify postgresql.conf in the new
cluster to match the old cluster.
Backpatch to 9.2.
Suggested by user.
Branch
--
REL9_2_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/
pg_upgrade docs: mention modification of postgresql.conf in new cluster
Mention it might be necessary to modify postgresql.conf in the new
cluster to match the old cluster.
Backpatch to 9.2.
Suggested by user.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/a11e15c
Restrict infomask bits to set on multixacts
We must only set the bit(s) for the strongest lock held in the tuple;
otherwise, a multixact containing members with exclusive lock and
key-share lock will behave as though only a share lock is held.
This bug was introduced in commit 0ac5ad5134, somewhe
pgrowlocks: fix bogus lock strength output
Per report from [email protected]
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/77a3082fc546774808b76f58173caec3852ebf62
Modified Files
--
contrib/pgrowlocks/pgrowlocks.c | 11 ---
1 files changed, 8 ins
PL/Tcl: Fix compiler warnings with Tcl 8.6
Some constification was added in the Tcl APIs, so add the modifiers in
PL/Tcl as well.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/b1980f6d03f79ab57da8f32aa8cd9677dbe1d58f
Modified Files
--
src/pl/tcl/pltcl.
Add CREATE RECURSIVE VIEW syntax
This is specified in the SQL standard. The CREATE RECURSIVE VIEW
specification is transformed into a normal CREATE VIEW statement with a
WITH RECURSIVE clause.
reviewed by Abhijit Menon-Sen and Stephen Frost
Branch
--
master
Details
---
http://git.postg
16 matches
Mail list logo
