On Mon, Dec 11, 2017 at 12:07 PM, Jeff Janes wrote:
> On Tue, Dec 5, 2017 at 5:50 PM, Thomas Munro
> wrote:
>> The problem is that our logic (1) focuses on when we should *start*
>> freezing, not by when we'd like to be finished, and (2) is defined in
>> such a way that many tables are likely to
On Tue, Dec 5, 2017 at 5:50 PM, Thomas Munro
wrote:
> On Tue, Dec 5, 2017 at 5:43 PM, Jeff Janes wrote:
> > On Mon, Dec 4, 2017 at 5:52 PM, John R Pierce
> wrote:
> >> On 12/4/2017 2:21 PM, chris kim wrote:
> >>> How would I investigate if my database is nearing a transaction wrap
> >>> around.
On Tue, Dec 5, 2017 at 5:43 PM, Jeff Janes wrote:
> On Mon, Dec 4, 2017 at 5:52 PM, John R Pierce wrote:
>> On 12/4/2017 2:21 PM, chris kim wrote:
>>> How would I investigate if my database is nearing a transaction wrap
>>> around.
>>
>> it would be screaming bloody murder in the log, for one.
>>
On Mon, Dec 4, 2017 at 5:52 PM, John R Pierce wrote:
> On 12/4/2017 2:21 PM, chris kim wrote:
>
>>
>>
>> How would I investigate if my database is nearing a transaction wrap
>> around.
>>
>
>
> it would be screaming bloody murder in the log, for one.
>
>
Unfortunately, that comes far too late to
John R Pierce writes:
> On 12/4/2017 2:21 PM, chris kim wrote:
>> How would I investigate if my database is nearing a transaction wrap
>> around.
> it would be screaming bloody murder in the log, for one.
I think the simplest thing is to keep an eye on
select max(age(datfrozenxid)) fro
On 12/4/2017 2:21 PM, chris kim wrote:
How would I investigate if my database is nearing a transaction wrap
around.
it would be screaming bloody murder in the log, for one.
--
john r pierce, recycling bits in santa cruz
