Mika Eloranta writes:
> On 02 Dec 2013, at 01:56, Tom Lane wrote:
>> * any other items that need to be corrected or expanded?
> I think 2103430 (Fix parsing of xlog file name in pg_receivexlog) is worth
> mentioning,
> as all past pg_receivexlog 9.3.x versions fail to resume interrupted
> str
On 2013-12-02 10:51:28 -0800, Josh Berkus wrote:
> Tom,
>
> "The issue can be ameliorated by, after upgrading, vacuuming all tables
> in all databases while having vacuum_freeze_table_age set to zero. "
>
> Why not say:
>
> "This issue can be ameliorated by, after upgrading, running a
> database
Tom,
"The issue can be ameliorated by, after upgrading, vacuuming all tables
in all databases while having vacuum_freeze_table_age set to zero. "
Why not say:
"This issue can be ameliorated by, after upgrading, running a
database-wide VACUUM FREEZE."
Or is there a difference in this case? If s
On 02 Dec 2013, at 01:56, Tom Lane wrote:
>
> * any other items that need to be corrected or expanded?
I think 2103430 (Fix parsing of xlog file name in pg_receivexlog) is worth
mentioning,
as all past pg_receivexlog 9.3.x versions fail to resume interrupted streaming
after ~4 GiB
of xlogs ha
On 2013-12-02 12:26:25 -0500, Tom Lane wrote:
> Andres Freund writes:
> > I think it might be worth mentioning that (parts) of the data are
> > potentially recoverable without too much effort in all of the bugs.
>
> I thought about that but was afraid that it'd come off like a commercial
> for da
Andres Freund writes:
> On 2013-12-01 18:56:19 -0500, Tom Lane wrote:
>> * is it useful to go into more detail than this about the data corruption
>> bugs? It's not clear to me that we can say more than "vacuum and re-clone
>> your standbys" as far as recovery actions go, at least not within the
Sergey Burladyan writes:
> Is it possible to fix my surname in changelog?
> -Sergey Burladyn
> +Sergey Burladyan
Oh, sorry about that! I can't do anything about the typo in the commit
log, but certainly we can get it right in the release notes.
regards, tom lane
--
Se
On Mon, Dec 2, 2013 at 4:56 AM, Tom Lane wrote:
> Andres Freund writes:
> > On 2013-12-01 18:56:19 -0500, Tom Lane wrote:
> >> I'd like to do any required editing on the notes at this stage,
> >> before I start extracting relevant subsets for the older branches.
>
> > When do you plan to backpat
Andres Freund writes:
> On 2013-12-01 18:56:19 -0500, Tom Lane wrote:
>> I'd like to do any required editing on the notes at this stage,
>> before I start extracting relevant subsets for the older branches.
> When do you plan to backpatch the documentation?
Tomorrow afternoon (my time).
On 2013-12-01 18:56:19 -0500, Tom Lane wrote:
> I've put up draft notes at
> http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=23e796de15567e9d31e8f9e8661828179f24a7be
> and they should be visible on the docs website at
> http://www.postgresql.org/docs/devel/static/release-9-3-2.htm
I've put up draft notes at
http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=23e796de15567e9d31e8f9e8661828179f24a7be
and they should be visible on the docs website at
http://www.postgresql.org/docs/devel/static/release-9-3-2.html
in half an hour or so, after guaibasaurus does its n
11 matches
Mail list logo
