From: | David Steele <david(at)pgmasters(dot)net> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby |
Date: | 2016-03-14 17:46:40 |
Message-ID: | 56E6F900.1090809@pgmasters.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | Postg토토 꽁 머니SQL : Postg토토 꽁 머니SQL 메일 링리스트 : 2016-03-14 이후 PGSQL-BUGS 17:46 Postg범퍼카 토토SQL |
On 2/24/16 12:40 AM, Michael Paquier wrote:
> This has the merit to be clear, thanks for the input. Whatever the
> approach taken at the end we have two candidates:
> - Extend XLogInsert() with an extra argument for flags (Andres)
> - Introduce XLogInsertExtended with this extra argument and let
> XLogInsert() in peace (Robert and I).
> Actually, I lied, there was still something I could do for this
> thread: attached are two patches implementing both approaches as
> respectively a-1 and a-2. Patch b is the set of logs I used for the
> tests to show with a low checkpoint_timeout that checkpoints are
> getting correctly skipped on an idle system.
Unfortunately neither A nor B apply anymore.
However, since the patches can still be read through I wonder if Robert
or Andres would care to opine on whether A or B is better now that they
can see the full implementation?
For my 2c I'm happy with XLogInsertExtended() since it seems to be a
rare use case where flags are required. This can always be refactored
in the future if/when the use of flags spreads.
I think it would be good to make a decision on this before asking
Michael to rebase.
Thanks,
--
-David
david(at)pgmasters(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | b.yordanov2 | 2016-03-14 20:43:48 | BUG #14020: row_number() over(partition by order by) - weird behavior |
Previous Message | Tom Lane | 2016-03-14 15:16:29 | Re: BUG #14019: Security label TAB causes unexpected EOF and client session termination |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2016-03-14 17:54:09 | Re: Reworks of CustomScan serialization/deserialization |
Previous Message | Robert Haas | 2016-03-14 17:43:47 | Re: WIP: Upper planner pathification |