Prevent intermittent hang in recovery from bgwriter interaction.
Startup process waited for cleanup lock but when hot_standby = off
the pid was not registered, so that the bgwriter would not wake
the waiting process as intended.
Branch
--
master
Details
---
http://git.postgresql.org/pg/co
Prevent intermittent hang in recovery from bgwriter interaction.
Startup process waited for cleanup lock but when hot_standby = off
the pid was not registered, so that the bgwriter would not wake
the waiting process as intended.
Branch
--
REL9_0_STABLE
Details
---
http://git.postgresql.or
Remove synchronous_replication/max_wal_senders cross-check.
This is no longer necessary, and might result in a situation where the
configuration file is reloaded (and everything seems OK) but a subsequent
restart of the database fails.
Per an observation from Fujii Masao.
Branch
--
master
D
Fix ancient typo in user-defined-aggregates documentation.
The description of the initcond value for the built-in avg(float8)
aggregate has been wrong since it was written. Noted by Disc Magnet.
Branch
--
REL8_4_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/e39d6db39b958381
Fix ancient typo in user-defined-aggregates documentation.
The description of the initcond value for the built-in avg(float8)
aggregate has been wrong since it was written. Noted by Disc Magnet.
Branch
--
REL9_0_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/6d0877fc5e5847e2
Fix ancient typo in user-defined-aggregates documentation.
The description of the initcond value for the built-in avg(float8)
aggregate has been wrong since it was written. Noted by Disc Magnet.
Branch
--
REL8_3_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/03f957fe1d10
Fix ancient typo in user-defined-aggregates documentation.
The description of the initcond value for the built-in avg(float8)
aggregate has been wrong since it was written. Noted by Disc Magnet.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/ba7d020d9d6edba872173f8
Fix ancient typo in user-defined-aggregates documentation.
The description of the initcond value for the built-in avg(float8)
aggregate has been wrong since it was written. Noted by Disc Magnet.
Branch
--
REL8_2_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/24cdee8606086699
On 23 March 2011 16:34, Tom Lane wrote:
> Fix ancient typo in user-defined-aggregates documentation.
>
> The description of the initcond value for the built-in avg(float8)
> aggregate has been wrong since it was written. Noted by Disc Magnet.
>
> Branch
> --
> REL8_2_STABLE
>
> Details
>
Thom Brown writes:
> On 23 March 2011 16:34, Tom Lane wrote:
>> Fix ancient typo in user-defined-aggregates documentation.
>>
>> The description of the initcond value for the built-in avg(float8)
>> aggregate has been wrong since it was written. Noted by Disc Magnet.
> The preceding paragraph
Minor changes to recovery pause behaviour.
Change location LOG message so it works each time we pause, not
just for final pause.
Ensure that we pause only if we are in Hot Standby and can connect
to allow us to run resume function. This change supercedes the
code to override parameter recoveryPause
Improve user-defined-aggregates documentation.
On closer inspection, that two-element initcond value seems to have been
a little white lie to avoid explaining the full behavior of float8_accum.
But if people are going to expect the examples to be exactly correct,
I suppose we'd better explain. Pe
Improve user-defined-aggregates documentation.
On closer inspection, that two-element initcond value seems to have been
a little white lie to avoid explaining the full behavior of float8_accum.
But if people are going to expect the examples to be exactly correct,
I suppose we'd better explain. Pe
Improve user-defined-aggregates documentation.
On closer inspection, that two-element initcond value seems to have been
a little white lie to avoid explaining the full behavior of float8_accum.
But if people are going to expect the examples to be exactly correct,
I suppose we'd better explain. Pe
Improve user-defined-aggregates documentation.
On closer inspection, that two-element initcond value seems to have been
a little white lie to avoid explaining the full behavior of float8_accum.
But if people are going to expect the examples to be exactly correct,
I suppose we'd better explain. Pe
Improve user-defined-aggregates documentation.
On closer inspection, that two-element initcond value seems to have been
a little white lie to avoid explaining the full behavior of float8_accum.
But if people are going to expect the examples to be exactly correct,
I suppose we'd better explain. Pe
On 23 March 2011 20:58, Tom Lane wrote:
> Improve user-defined-aggregates documentation.
>
> On closer inspection, that two-element initcond value seems to have been
> a little white lie to avoid explaining the full behavior of float8_accum.
> But if people are going to expect the examples to be e
17 matches
Mail list logo
