Reset master xmin when hot_standby_feedback disabled.
If walsender has xmin of standby then ensure we
reset the value to 0 when we change from hot_standby_feedback=on
to hot_standby_feedback=off.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/bd56e74127dea4102d1fc761
Tom Lane wrote:
> Alvaro Herrera writes:
> > Move Assert() definitions to c.h
>
> This seems a bit odd. Why didn't you move all of postgres.h's section 3
> into the new section in c.h? The couple of declarations you left there
> are neither useful nor intelligible on their own.
One slight prob
Alvaro Herrera writes:
> Tom Lane wrote:
>> This seems a bit odd. Why didn't you move all of postgres.h's section 3
>> into the new section in c.h? The couple of declarations you left there
>> are neither useful nor intelligible on their own.
> One slight problem in this line:
> extern PGDLLIM
Reset vacuum_defer_cleanup_age to PGC_SIGHUP.
Revert commit 84725aa5efe11688633b553e58113efce4181f2e
Branch
--
REL9_1_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/2113574be8467e044a74b7eb4da6841e78384e2e
Modified Files
--
doc/src/sgml/config.sgml |3 ++-
Reset vacuum_defer_cleanup_age to PGC_SIGHUP.
Revert commit 84725aa5efe11688633b553e58113efce4181f2e
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/f480e294498533820f3ef3e6de4dcb8ff5401140
Modified Files
--
doc/src/sgml/config.sgml |3 ++-
src/bac
Reset vacuum_defer_cleanup_age to PGC_SIGHUP.
Revert commit 84725aa5efe11688633b553e58113efce4181f2e
Branch
--
REL9_0_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/e3729932ebc4ed4ab2a9278fc8bb162c1f25fa73
Modified Files
--
doc/src/sgml/config.sgml |3 ++-
Reset vacuum_defer_cleanup_age to PGC_SIGHUP.
Revert commit 84725aa5efe11688633b553e58113efce4181f2e
Branch
--
REL9_2_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/b5f6c4dbe023e769aef4669bc25bfb6310754602
Modified Files
--
doc/src/sgml/config.sgml |3 ++-
Update release notes for 9.2.3, 9.1.8, 9.0.12, 8.4.16, 8.3.23.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/318db6b2a05ca12d7ca7bae288bf473def4bdd42
Modified Files
--
doc/src/sgml/release-8.3.sgml | 156 +++
doc/src/sgml/release-8.4.sgml |
Update release notes for 9.2.3, 9.1.8, 9.0.12, 8.4.16, 8.3.23.
Branch
--
REL9_2_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/23ab69922652a9f6f6bbd1fe254081fa6a6e089f
Modified Files
--
doc/src/sgml/release-8.3.sgml | 156 +++
doc/src/sgml/release-8.4.
Update release notes for 9.2.3, 9.1.8, 9.0.12, 8.4.16, 8.3.23.
Branch
--
REL9_0_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/0499ff2567475ccd93b07183d4bb44d29ba1c006
Modified Files
--
doc/src/sgml/release-8.3.sgml | 156 ++
doc/src/sgml/r
Update release notes for 9.2.3, 9.1.8, 9.0.12, 8.4.16, 8.3.23.
Branch
--
REL8_3_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/fea63237515c31f6f8d91c7bb15b03e527017198
Modified Files
--
doc/src/sgml/release-8.3.sgml | 156 +
Update release notes for 9.2.3, 9.1.8, 9.0.12, 8.4.16, 8.3.23.
Branch
--
REL9_1_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/51d0efe8a2bd6c64f245fcc60a2fba07b9e3b6f6
Modified Files
--
doc/src/sgml/release-8.3.sgml | 156 +
doc/src/sgml/releas
Update release notes for 9.2.3, 9.1.8, 9.0.12, 8.4.16, 8.3.23.
Branch
--
REL8_4_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/90f77d759b5b394ec477f634ba6ece03dbd0574e
Modified Files
--
doc/src/sgml/release-8.3.sgml | 156
doc/src/
Stamp 9.2.3.
Branch
--
REL9_2_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/51dac56ad5fd4cf5fe90f59c4b40f967fc3b13c5
Modified Files
--
configure| 18 +-
configure.in |2 +-
doc/bug.template
Stamp 8.4.16.
Branch
--
REL8_4_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/2228ce6a11def75e11f0232592848614f27bd7dc
Modified Files
--
configure| 18 +-
configure.in |2 +-
doc/bug.template
Stamp 9.0.12.
Branch
--
REL9_0_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/3da04a0bb19f8543a9b13becdfeb96624e15288e
Modified Files
--
configure| 18 +-
configure.in |2 +-
doc/bug.template
Stamp 8.3.23.
Branch
--
REL8_3_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/0caf5629699104b94854a5cbb203a37227b2d763
Modified Files
--
configure| 18 +-
configure.in |2 +-
doc/bug.template
Stamp 9.1.8.
Branch
--
REL9_1_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/69c026512f1141a92dca118768d858e59d76a994
Modified Files
--
configure| 18 +-
configure.in |2 +-
doc/bug.template
On 4 February 2013 21:29, Tom Lane wrote:
> Stamp 9.1.8.
Did you not get my mail about me being in the middle of backpatching?
I guess I can stop now.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-
Simon Riggs writes:
> On 4 February 2013 21:29, Tom Lane wrote:
>> Stamp 9.1.8.
> Did you not get my mail about me being in the middle of backpatching?
> I guess I can stop now.
4pm on the day of a release is way too late to be committing anything
(except security stuff ...). If you felt you
On Mon, Feb 4, 2013 at 9:40 PM, Tom Lane wrote:
> Simon Riggs writes:
>> On 4 February 2013 21:29, Tom Lane wrote:
>>> Stamp 9.1.8.
>
>> Did you not get my mail about me being in the middle of backpatching?
>
>> I guess I can stop now.
>
> 4pm on the day of a release is way too late to be commit
On 4 February 2013 21:40, Tom Lane wrote:
> Simon Riggs writes:
>> On 4 February 2013 21:29, Tom Lane wrote:
>>> Stamp 9.1.8.
>
>> Did you not get my mail about me being in the middle of backpatching?
>
>> I guess I can stop now.
>
> 4pm on the day of a release is way too late to be committing a
On 4 February 2013 21:48, Dave Page wrote:
> We should really freeze the code for 24 hours shouldn't we? That way
> we know most, if not all of the buildfarm animals will have had a
> chance to go red since the last code change.
Do whatever you like, as long as you tell me about it.
--
Simon
On 02/04/2013 04:49 PM, Simon Riggs wrote:
On 4 February 2013 21:40, Tom Lane wrote:
Simon Riggs writes:
On 4 February 2013 21:29, Tom Lane wrote:
Stamp 9.1.8.
Did you not get my mail about me being in the middle of backpatching?
I guess I can stop now.
4pm on the day of a release is way
Simon Riggs writes:
> On 4 February 2013 21:48, Dave Page wrote:
>> We should really freeze the code for 24 hours shouldn't we? That way
>> we know most, if not all of the buildfarm animals will have had a
>> chance to go red since the last code change.
> Do whatever you like, as long as you tel
On 4 February 2013 22:13, Tom Lane wrote:
> Simon Riggs writes:
>> On 4 February 2013 21:48, Dave Page wrote:
>>> We should really freeze the code for 24 hours shouldn't we? That way
>>> we know most, if not all of the buildfarm animals will have had a
>>> chance to go red since the last code ch
Andrew Dunstan writes:
> I agree it can be hard to keep the dates in mind. Could we add a couple
> of reminders for committers to the release procedures? Say 48 hours
> before the release to say "the tree needs to go quiet in 24 hours" and
> 24 hours before to say "no commits without discussion
On Mon, Feb 4, 2013 at 11:14:51PM -0500, Tom Lane wrote:
> What perhaps *could* use a little more process IMO is the release notes.
> While we do put a fair amount of effort into the notes for major
> releases, the process for minor-release notes has generally been that
> either Bruce or I run aro
28 matches
Mail list logo