| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Logical decoding of TRUNCATE |
| Date: | 2018-04-02 21:04:47 |
| Message-ID: | B360BD7D-D39C-46F0-B4CD-BCA76CBB09A3@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
> On Apr 2, 2018, at 11:50, Andres Freund <andres(at)anarazel(dot)de> wrote:
> I'm not convinced. I think it's perfectly reasonable to want to truncate
> away data on the live node, but maintain it on an archival node.
+1. We've had at least one specific request for this, in maintaining a data warehouse from an OLTP system.
--
-- Christophe Pettus
xof(at)thebuild(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-04-03 02:43:43 | Re: PostgreSQL Cascade streaming replication problem |
| Previous Message | Tom Lane | 2018-04-02 19:13:56 | Re: How to get an inclusive interval when using daterange |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2018-04-02 21:09:21 | Re: Add default role 'pg_access_server_files' |
| Previous Message | Stephen Frost | 2018-04-02 21:01:08 | Re: Disabling memory display in EXPLAIN ANALYZE |