Re: Make relfile tombstone files conditional on WAL level

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Make relfile tombstone files conditional on WAL level
Date: 2021-06-10 10:47:49
Message-ID: a8393e32-f378-97a5-a3a7-d07d6077757e@iki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 05/03/2021 00:02, Thomas Munro wrote:
> Hi,
>
> I'm starting a new thread for this patch that originated as a
> side-discussion in [1], to give it its own CF entry in the next cycle.
> This is a WIP with an open question to research: what could actually
> break if we did this?

I don't see a problem.

It would indeed be nice to have some other mechanism to prevent the
issue with wal_level=minimal, the tombstone files feel hacky and
complicated. Maybe a new shared memory hash table to track the
relfilenodes of dropped tables.

- Heikki

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2021-06-10 11:38:55 Re: PostmasterIsAlive() in recovery (non-USE_POST_MASTER_DEATH_SIGNAL builds)
Previous Message Andrew Dunstan 2021-06-10 10:29:12 Re: AWS forcing PG upgrade from v9.6 a disaster