On Wed, May 6, 2020 at 10:20:57PM -0700, Noah Misch wrote: > On Wed, May 06, 2020 at 07:40:25PM -0400, Bruce Momjian wrote: > > On Tue, May 5, 2020 at 11:39:10PM -0700, Noah Misch wrote: > > > On Mon, May 04, 2020 at 11:16:00PM -0400, Bruce Momjian wrote: > > > > Allow skipping of WAL for new tables and indexes if wal_level is > > > > 'minimal' (Noah Misch) > > > > > > Kyotaro Horiguchi authored that one. (I committed it.) The commit > > > message > > > noted characteristics, some of which may deserve mention in the notes: > > > > Fixed. > > I don't see that change pushed (but it's not urgent).
I got stuck on Amit's partition items and my head couldn't process any more, so I went to bed, and just committed it now. I was afraid to have pending stuff uncommitted, but I am also hesitant to do a commit for each change. > > > - Crash recovery was losing tuples written via COPY TO. This fixes the > > > bug. > > > > This was not backpatched? > > Right. Oh. So you are saying we could lose COPY data on a crash, even after a commit. That seems bad. Can you show me the commit info? I can't find it. > > > - Out-of-tree table access methods will require changes. > > > > Uh, I don't think we mention those. > > Okay. This point is relatively-important. On the other hand, the table > access methods known to me have maintainers who follow -hackers. They may > learn that way. That was my thought. -- Bruce Momjian <br...@momjian.us> https://momjian.us EnterpriseDB https://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +
