Re: In-placre persistance change of a relation

Kyotaro Horiguchi <horikyota.ntt@gmail.com>

From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
To: Jakub.Wartak@tomtom.com
Cc: tsunakawa.takay@fujitsu.com, osumi.takamichi@fujitsu.com, sfrost@snowman.net, masao.fujii@oss.nttdata.com, ashutosh.bapat.oss@gmail.com, pgsql-hackers@lists.postgresql.org
Date: 2021-12-23T06:01:41Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. pg_dump: Refactor getIndexes()

  2. Optimize DropRelFileNodesAllBuffers() for recovery.

Attachments

At Wed, 22 Dec 2021 08:42:14 +0000, Jakub Wartak <Jakub.Wartak@tomtom.com> wrote in 
> I think there's slight omission:
...
> apparently reindex_index() params cannot be NULL - the same happens with switching persistent

Hmm. a3dc926009 has changed the interface. (But the name is also
changed after that.)

-reindex_relation(Oid relid, int flags, int options)
+reindex_relation(Oid relid, int flags, ReindexParams *params)

> I'll also try to give another shot to the patch early next year - as we are starting long Christmas/holiday break here 
> - with verifying WAL for GiST and more advanced setup (more crashes, and standby/archiving/barman to see 
> how it's possible to use wal_level=minimal <-> replica transitions). 

Thanks. I added TAP test to excecise the in-place persistence change.

have a nice holiday, Jakub!

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center