From: | Любен Каравелов <karavelov(at)mail(dot)bg> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [RFC] CREATE QUEUE (log-only table) for londiste/pgQ ccompatibility |
Date: | 2012-10-19 12:36:05 |
Message-ID: | e673b0d46aca6654c741d0bf7a82fa22.mailbg@beta.mail.bg |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
----- Цитат от Hannu Krosing (hannu(at)krosing(dot)net), на 19.10.2012 в
14:17 ----- On 10/19/2012 04:26 AM, Ants Aasma wrote:
On Thu, Oct 18, 2012 at 10:03 PM, Hannu Krosing wrote:
Hmm. Maybe we should think of implementing this as REMOTE TABLE, that
is a table which gets no real data stored locally but all insert got
through
WAL
and are replayed as real inserts on slave side.
FWIW, MySQL calls this exact concept the "black hole" storage engine.
In this case calling this WRITE ONLY TABLE does not seem so strange
anymore :)
Or even PERSISTENT WRITE ONLY TABLE to make the paradox more explicit.
Oracle call this "Streams" and they build application queues ("Advanced
queuing") and replication solution ("Advanced replication") on them.
Why not call the feature "STREAM TABLE"?
Best regards
--
Luben Karavelov
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2012-10-19 13:29:05 | Re: [BUG] False indication in pg_stat_replication.sync_state |
Previous Message | Amit Kapila | 2012-10-19 12:16:34 | Re: September 2012 commitfest |