Hi,
sqlsmith doesn't like commit 4b0d28de06:
,
| regression=> select * from pg_control_checkpoint();
| server closed the connection unexpectedly
| TRAP: FailedAssertion("!((atti->attalign) == 's')", File: "heaptuple.c",
Line: 126)
`
On a build with assertions disabled, the statement fai
On Wed, Nov 8, 2017 at 4:43 AM, Tom Lane wrote:
> Andres Freund writes:
>> I think you misunderstand my point - I'm saying that pg_resetxlog should
>> be able to force the use of older checkpoints, basically as a fallback
>> to cases where the previous approach might actually have worked, not
>>
Andres Freund writes:
> I think you misunderstand my point - I'm saying that pg_resetxlog should
> be able to force the use of older checkpoints, basically as a fallback
> to cases where the previous approach might actually have worked, not
> that it needs to work across format changes.
That seem
On 2017-11-07 14:12:19 -0500, Tom Lane wrote:
> Andres Freund writes:
> > On 2017-11-07 17:57:31 +, Simon Riggs wrote:
> >> Remove secondary checkpoint
>
> > FWIW, I don't think this should be applied without a pg_resetxlog
> > feature allowing to manually use older checkpoints.
>
> Uh, what
Andres Freund writes:
> On 2017-11-07 17:57:31 +, Simon Riggs wrote:
>> Remove secondary checkpoint
> FWIW, I don't think this should be applied without a pg_resetxlog
> feature allowing to manually use older checkpoints.
Uh, what? We have never before insisted on pg_resetxlog being able
to
On 2017-11-07 17:57:31 +, Simon Riggs wrote:
> Remove secondary checkpoint
>
> Previously server reserved WAL for last two checkpoints,
> which used too much disk space for small servers.
>
> Bumps PG_CONTROL_VERSION
FWIW, I don't think this should be applied without a pg_resetxlog
feature a
Remove secondary checkpoint
Previously server reserved WAL for last two checkpoints,
which used too much disk space for small servers.
Bumps PG_CONTROL_VERSION
Author: Simon Riggs
Reviewed-by: Michael Paquier
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/4b0d2
