Re: Suggestion: provide a "TRUNCATE PARTITION" command

From: Thiemo Kellner <thiemo(at)gelassene-pferde(dot)biz>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Suggestion: provide a "TRUNCATE PARTITION" command
Date: 2021-01-09 11:38:23
Message-ID: 20210109123823.Horde.LTOIGKJXshO7quow1ALLZ5f@webmail.gelassene-pferde.biz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Quoting Michael Lewis <mlewis(at)entrata(dot)com>:

> Still, no feedback on the effect that a truncate call is having on
> the DB and may be doing more than intended fairly easily. I am not
> in the hackers group so I couldn't say this feature would not be
> implemented. It just seems unlikely given the philosophies of that
> group.

I would not feel bad to have a more efficient option but possibly a
more dangerous one. Projects/application could setup policies about
what may be done in which way and what not.
S/MIME Public Key:
https://oc.gelassene-pferde.biz/index.php/s/eJuAUFONag6ofnH
Signal (Safer than WhatsApp): +49 1578 7723737
Threema (Safer than WhatsApp): A76MKH3J
Handys: +41 78 947 36 21 | +49 1578 772 37 37

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alexander Farber 2021-01-09 13:31:57 Select a column and then apply JSONB_ARRAY_ELEMENTS to it
Previous Message Paul Förster 2021-01-09 07:55:50 Re: Using more than one LDAP?