| From: | Ian Lawrence Barwick <barwick(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, David Zhang <david(dot)zhang(at)highgo(dot)ca>, Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Non-replayable WAL records through overflows and >MaxAllocSize lengths |
| Date: | 2022-11-04 00:52:39 |
| Message-ID: | CAB8KJ=ixvhJEXriMwUfRY6HU8CqUfkcJzmS2r2zt2nfU2HMqNg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2022年10月5日(水) 16:46 Michael Paquier <michael(at)paquier(dot)xyz>:
>
> Hi Matthias,
>
> On Wed, Jul 27, 2022 at 02:07:05PM +0200, Matthias van de Meent wrote:
>
> My apologies for the time it took me to come back to this thread.
> > > + * To accommodate some overhead, hhis MaxXLogRecordSize value allows for
> > > s/hhis/this/.
> >
> > Will be included in the next update..
>
> v8 fails to apply. Could you send a rebased version?
>
> As far as I recall the problems with the block image sizes are solved,
> but we still have a bit more to do in terms of the overall record
> size. Perhaps there are some parts of the patch you'd like to
> revisit?
>
> For now, I have switched the back as waiting on author, and moved it
> to the next CF.
Hi Matthias
CommitFest 2022-11 is currently underway, so if you are interested
in moving this patch forward, now would be a good time to update it.
Thanks
Ian Barwick
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Naylor | 2022-11-04 00:55:20 | Re: Incorrect include file order in guc-file.l |
| Previous Message | Ian Lawrence Barwick | 2022-11-04 00:47:09 | Re: [PATCH] New [relation] option engine |