| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | "Agarwal, Pragati - Dell Team" <Pragati(dot)A(at)dellteam(dot)com> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, "Silaparasetti, Ramesh" <Ramesh(dot)Silaparasetty(at)dell(dot)com>, "Kishore, Nanda - Dell Team" <Nanda(dot)Kishore(at)dellteam(dot)com>, "Mahendrakar, Prabhakar - Dell Team" <Prabhakar(dot)Mahendraka(at)dellteam(dot)com> |
| Subject: | Re: Very URGENT REQUEST - Postgresql error : PANIC: could not locate a valid checkpoint record |
| Date: | 2022-02-11 12:34:09 |
| Message-ID: | 20220211123409.2dwm64ppgzfopyta@jrouhaud |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Feb 11, 2022 at 11:19:54AM +0000, Agarwal, Pragati - Dell Team wrote:
> Hi Merlin, Julien
>
> Thanks for your response.
>
> Besides this, there is public schema in postgres which we are not using in
> our Datastore service.
>
> As a workaround of an upgrade process, we plan to drop the public schema. We
> would like to know your thoughts on this and any detrimental impact on the
> data or service.
I'm not sure how that's a workaround, but that schema isn't necessary for
postgres, it's just a schema that's created by default. You can remove it
without impact as long as you don't rely on it in any of your applications.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ryan Kelly | 2022-02-11 16:34:14 | Re: ERROR: XX000: variable not found in subplan target list |
| Previous Message | Agarwal, Pragati - Dell Team | 2022-02-11 11:19:54 | RE: Very URGENT REQUEST - Postgresql error : PANIC: could not locate a valid checkpoint record |