Re: ERROR: failed to find conversion function from key_vals_nn to record[]

On 2022-06-16 23:58:23 -0700, Bryn Llewellyn wrote: > david.g.johns...@gmail.com wrote: > > b...@yugabyte.com wrote: > > Can anybody show me an implementation of a realistic use case that > follows proper practice — like "every table must a primary key", "a > f

ISBN (was: '{"x": 42, "y": null}'::jsonb != '{"x": 42}'::jsonb ... Really?)

On 2022-06-17 17:14:14 -0700, Bryn Llewellyn wrote: > "isbn" — string > values must be unique across the entire set of documents (in other words, it > defines the unique business key); values must have this pattern: > > « ^[0-9]{3}-[0-9]{1}-[0-9]{2}-[0-9]{6}-[0-9]{1}$ » Completely off-topic, bu

Re: '{"x": 42, "y": null}'::jsonb != '{"x": 42}'::jsonb ... Really?

> mmonc...@gmail.com wrote: > > yeah. I would expect for json or jsonb, two values, "a, b", "a" is distinct > from "b" should give the same answer as "a::text is distinct from b::text". > >> t...@sss.pgh.pa.us wrote: >> >>> b...@yugabyte.

Re: Operators on ranges with a domain subtype do not implicitly cast operands of the domain's base type

pá 17. 6. 2022 v 17:26 odesílatel Daniel Popowich napsal: > On Thu, Jun 16, 2022 at 4:26 PM Tom Lane wrote: > >> Daniel Popowich writes: >> > -- domain with underlying type of integer (what constraints we might >> > -- place on the integer values are not germane to the issue so >> they'

Re: Operators on ranges with a domain subtype do not implicitly cast operands of the domain's base type

On Thu, Jun 16, 2022 at 4:26 PM Tom Lane wrote: > Daniel Popowich writes: > > -- domain with underlying type of integer (what constraints we might > > -- place on the integer values are not germane to the issue so > they're > > -- left out). > > create domain zzzint integer; > >

RE: Postgresql error : PANIC: could not locate a valid checkpoint record

Yes, We are using the pg_upgrade utility of Postgres. From: Mateusz Henicz Sent: Friday, June 17, 2022 3:31 PM To: Mahendrakar, Prabhakar - Dell Team Cc: pgsql-general@lists.postgresql.org Subject: Re: Postgresql error : PANIC: could not locate a valid checkpoint record [EXTERNAL EMAIL] Hi, Ha

Re: Postgresql error : PANIC: could not locate a valid checkpoint record

On Fri, 2022-06-17 at 06:35 +, Mahendrakar, Prabhakar - Dell Team wrote: > We are facing checkpoint related issues from PostGreSQL 13.4 ( could not > locate a valid checkpoint record) and Postgres service fails to come up. > =

Re: Postgresql error : PANIC: could not locate a valid checkpoint record

Assuming you have shut down your postgres properly before upgrading, it should be safe for you to run pg_resetwal. https://www.postgresql.org/docs/current/app-pgresetwal.html It should help in this case. pt., 17 cze 2022 o 12:03 Mahendrakar, Prabhakar - Dell Team < prabhakar.mahendr...@dellteam.co

Re: Postgresql error : PANIC: could not locate a valid checkpoint record

Hi, Have you done pg_upgrade post Postgres 13 installation? https://www.postgresql.org/docs/13/pgupgrade.html Cheers, Mateusz pt., 17 cze 2022 o 11:20 Mahendrakar, Prabhakar - Dell Team < prabhakar.mahendr...@dellteam.com> napisał(a): > Hello, > > > > Good Morning ! > > > > We are facing *check

Postgresql error : PANIC: could not locate a valid checkpoint record

Hello, Good Morning ! We are facing checkpoint related issues from PostGreSQL 13.4 ( could not locate a valid checkpoint record) and Postgres service fails to come up. LOG: starting PostgreS