; set together, is now defined as HEAP_XMIN_FROZEN.
But we still have FrozenTransactionId mentioned in section 23.1.5.
Please consider the attached patch to fix it.
Thanks,
Egor Rogov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
diff --git a/doc/src/sgml/maintenan
tstatements">.
>
> Is it correct? Shouldn't the TIMING option be mentioned there instead
> of
> BUFFERS?
Yes, it's correct. Track_io_timing parameter corresponds to the buffer
manager. With BUFFERS option EXPLAIN shows buffers usage; when
track_io_timing is on it al
Hi,
This documentation bug is still in place for upcoming 9.6. Aren't anyone
interested in fixing it?
Regards,
Egor Rogov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
--
View this message in context:
http://postgresql.nabble.com/FrozenTransact
ed. I hope it is a bit easier to review now.
Regards,
Egor Rogov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
maintenance-2.patch (2K)
<http://postgresql.nabble.com/attachment/5919578/0/maintenance-2.patch>
--
View this message in context:
http://postgr
Sorry, my last email went without the attachment.
On 06.09.2016 01:09, Egor Rogov wrote:
Tom Lane <[hidden email]
> writes:
> It'd be more likely to get pushed if you'd submitted it in an easily
> reviewable form, ie without reflowing the entire (rather long)
paragrap
On 06.09.2016 15:41, Tom Lane wrote:
Egor Rogov writes:
Please find another patch attached. I hope it is a bit easier to
review now.
Hmm. I do not actually see anything wrong with the existing text:
it does not say that FrozenTransactionId is what appears on disk,
it says that frozen tuples
On 06.09.2016 23:41, Tom Lane wrote:
Egor Rogov writes:
Right, it does not say that FrozenTransactionId is what appears on disk,
but what is? There is no such information anywhere in the doc. Since 9.4
frozen transactions have their normal XIDs preserved, so how a user can
tell normal
