| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Online DW |
| Date: | 2016-06-10 13:32:54 |
| Message-ID: | CAMsr+YGUH69c5EBkERaegn+v2Kagy=y-b1S3j6LufN-wqfnfHg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On 10 June 2016 at 18:56, John R Pierce <pierce(at)hogranch(dot)com> wrote:
> On 6/10/2016 2:18 AM, Sridhar N Bamandlapally wrote:
>
>> This/These will be performed in Production to clean-up archive which will
>> not be sync with Archive/DW DB only
>>
>> one heads-up is Archive/DW DB may need to build WITHOUT CONSTRAINTS
>>
>> May need to introduce ARCHIVE system/tag in pg_hba.conf
>>
>
> there's a whole lot of implied magic here unless you want to get way more
> specific what these features do, exactly, under all possible conditions.
I'd go further than that and say I can't see how something like this could
possibly work with physical (block based) replication. It's total
hand-waving.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2016-06-10 14:48:28 | pgAdmin 4 v1.0 Beta 1 Released |
| Previous Message | Adrian Klaver | 2016-06-10 13:17:00 | Re: Changelog version from 8.1.2 to 9.3.6 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2016-06-10 14:45:01 | Re: [HACKERS] Re: pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold < |
| Previous Message | Amit Kapila | 2016-06-10 13:27:31 | Re: Reviewing freeze map code |