| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Prabhat Sahu <prabhat(dot)sahu(at)enterprisedb(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Server crash with Master-Slave configuration. |
| Date: | 2019-12-28 02:46:09 |
| Message-ID: | CA+TgmoaG6osCKjpSFN+P6DOdjwsW_0MpqCtio0kXA=5XMHqhgg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Dec 25, 2019 at 1:29 AM Prabhat Sahu <prabhat(dot)sahu(at)enterprisedb(dot)com>
wrote:
> Thanks Michael for pointing it out, I have re-tested the scenario
> with "--tablespace-mapping=OLDDIR=NEWDIR" option of pg_basebackup, and now
> its working fine.
> But I think, instead of the crash, a proper error message would be
> better.
>
It appears from the stack trace you sent that it emits a PANIC, which seems
like a proper error message to me.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2019-12-28 03:01:14 | Allow WHEN in INSTEAD OF triggers |
| Previous Message | David Fetter | 2019-12-28 02:16:48 | Re: use CLZ instruction in AllocSetFreeIndex() |