On Tue, Jan 14, 2014 at 2:39 AM, Amit Kapila wrote:
> On Fri, Jan 3, 2014 at 9:02 PM, Peter Eisentraut wrote:
>> On 12/17/13, 8:16 PM, Maciek Sakrejda wrote:
>>> (now with patch--sorry about that)
>>
>> This patch doesn't apply.
>
> There are some recent changes around same place which broke this
On Fri, Jan 3, 2014 at 9:02 PM, Peter Eisentraut wrote:
> On 12/17/13, 8:16 PM, Maciek Sakrejda wrote:
>> (now with patch--sorry about that)
>
> This patch doesn't apply.
There are some recent changes around same place which broke this
patch. Please find the modified patch attached with this mail
On 12/17/13, 8:16 PM, Maciek Sakrejda wrote:
> (now with patch--sorry about that)
This patch doesn't apply.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Wed, Dec 18, 2013 at 6:46 AM, Maciek Sakrejda wrote:
>VACUUM FREEZE sets both vacuum_freeze_min_age and vacuum_freeze_table_age to
>0, but only the former is documented. This patch notes that the other setting
>is also affected.
> (now with patch--sorry about that)
Your explanation and patch
(now with patch--sorry about that)
diff --git a/doc/src/sgml/ref/vacuum.sgml b/doc/src/sgml/ref/vacuum.sgml
index eb71581..5f03343 100644
--- a/doc/src/sgml/ref/vacuum.sgml
+++ b/doc/src/sgml/ref/vacuum.sgml
@@ -100,8 +100,9 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] ANALYZE [
Select
VACUUM FREEZE sets both vacuum_freeze_min_age and vacuum_freeze_table_age
to 0, but only the former is documented. This patch notes that the other
setting is also affected.
