| From: | Ian Barwick <ian(at)2ndquadrant(dot)com> |
|---|---|
| To: | Sreekanth Palluru <Sreekanth(dot)Palluru(at)superchoice(dot)com(dot)au>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Testing hot standby on same server sharing same tablespace directory |
| Date: | 2016-04-28 01:55:26 |
| Message-ID: | 57216D8E.2080907@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On 04/28/2016 08:45 AM, Sreekanth Palluru wrote:
>
> Hi
>
> I am testing hot standby on same server (version 9.5.2) , everything works well.
> I have a doubt regarding sharing of tablespace directory by these two databases .
>
> I have created a tablespace and moved few objects and I happen to see that same
> directory was being used by standby node aka slave node and to my surprise it still works
> without any issues.
>
> Is this expected ?
Both instances will start and initially appear to function, but you are guaranteed
to run into unexpected behaviour and some kind of corruption.
Try e.g. creating and populating a table, then pausing replay on the standby; then
drop and recreate/repopulate the same table.
> I was expecting some sort of warnings from Postgres or am I missing something
No, there's nothing which could warn about this particular scenario.
Regards
Ian Barwick
--
Ian Barwick http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sreekanth Palluru | 2016-04-28 04:57:23 | Re: Testing hot standby on same server sharing same tablespace directory |
| Previous Message | Sreekanth Palluru | 2016-04-27 23:45:18 | Testing hot standby on same server sharing same tablespace directory |