Re: PL/pgSQL: Spurious 22P02 error on "select col into var" when col is user-defined type

> On 10-Aug-2021, at 13:12, Pavel Stehule wrote: > > >> >> r := (select (b, t)::type1 -- it is composite with labels again > > > postgres=# do $$ > declare r record; > begin > r := (select (10,20)); > raise notice '%', to_json(r); > end; > $$; > NOTICE: {"f1":10,"f2":20} > DO > postgres=

Re: PL/pgSQL: Spurious 22P02 error on "select col into var" when col is user-defined type

> > r := (select (b, t)::type1 -- it is composite with labels again > > > postgres=# do $$ declare r record; begin r := (select (10,20)); raise notice '%', to_json(r); end; $$; NOTICE: {"f1":10,"f2":20} DO postgres=# do $$ declare r record; begin r := (select (10,20)::footype); raise notic

Re: PL/pgSQL: Spurious 22P02 error on "select col into var" when col is user-defined type

> pavel.steh...@gmail.com wrote: > > b...@yugabyte.com wrote: > >> pavel.steh...@gmail.com wrote: >> >>> t...@sss.pgh.pa.us wrote: >>> pavel.steh...@gmail.com wrote: >>>

Re: PL/pgSQL: Spurious 22P02 error on "select col into var" when col is user-defined type

út 10. 8. 2021 v 21:25 odesílatel Pavel Stehule napsal: > >>> I can get the reference by field name that I prefer with a schema-level >>> type: >>> >>> create type tmp as (b text, t type1); >>> >>> and by declaring "r" with this data type. But this is a greater >>> discomfort than using the dynam

Re: PL/pgSQL: Spurious 22P02 error on "select col into var" when col is user-defined type

po 9. 8. 2021 v 23:13 odesílatel Tom Lane napsal: > Pavel Stehule writes: > > Some errors like this, but not this can be detected by plpgsql_check > > https://github.com/okbob/plpgsql_check - probably the heuristic for type > > check is not complete. > > STRICTMULTIASSIGNMENT would detect most c

Re: PL/pgSQL: Spurious 22P02 error on "select col into var" when col is user-defined type

> > >> I can get the reference by field name that I prefer with a schema-level >> type: >> >> create type tmp as (b text, t type1); >> >> and by declaring "r" with this data type. But this is a greater >> discomfort than using the dynamically shaped "record" because it needs you >> to create a dedi

Re: PL/pgSQL: Spurious 22P02 error on "select col into var" when col is user-defined type

út 10. 8. 2021 v 19:48 odesílatel Bryn Llewellyn napsal: > pavel.steh...@gmail.com wrote: > > t...@sss.pgh.pa.us wrote: > > *pavel.steh...@gmail.com wrote:* > > Some errors like this, but not this can be detected by plpgsql_check > https://github.com/okbob/plpgsql_check > probably the heuristic

Re: PL/pgSQL: Spurious 22P02 error on "select col into var" when col is user-defined type

> pavel.steh...@gmail.com wrote: > >> t...@sss.pgh.pa.us wrote: >> >>> pavel.steh...@gmail.com wrote: >>> >>> Some errors like this, but not this can be detected by plpgsql_check >>> https://github.com/okbob/plpgsql_check >>> probably the heuristic for type check is not complete. >> >> STRICTMU

Re: archive_command / single user mode

> On Aug 9, 2021, at 18:03, David G. Johnston > wrote: > > On Mon, Aug 9, 2021 at 4:17 PM Christophe Pettus wrote: >> Does archive_command run in single user mode? This isn't an actual >> situation at the moment, but for runbook / disaster planning purposes, I was >> curious. > > > Nope

Re: php connection failure

On 8/10/21 1:59 AM, ourdiaspora wrote: On Sunday, August 8th, 2021 at 1:51 AM, Adrian Klaver wrote: 1. Get rid of the first local line . 2. Then for the remaining local line below change peer to trust and restart Postgres. Thank you, but repeat error occurred: sudo sudo service po

Re: php connection failure

ourdiaspora writes: > A quick ddg search revealed: > sudo ss -tulpn > Netid State Recv-Q Send-Q Local Address:Port Peer > Address:Port > tcpLISTEN 0 128 ::1:5432 :::* >users:(("postgres",pid=21794,fd=3)) > Is the correct c

Re: (13.1) pg_basebackups ./. pg_verifybackup

El día martes, agosto 10, 2021 a las 09:23:34a. m. +0200, Matthias Apitz escribió: > I've studied now the fine docs again and have some additional questions. The > backup was done fine to the directory /data/postgresql133/backup-20210810-1 > which contains now: > > $ ls -l

Re: php connection failure

On Sunday, August 8th, 2021 at 2:15 AM, Tom Lane wrote: > ourdiaspora ourdiasp...@protonmail.com writes: > > > psql -d cpacweb -U cpaca > > > > psql: FATAL: Peer authentication failed for user "cpaca" > > It's a gold > > plated certainty that the default packet filter configuration > > wouldn

Re: php connection failure

On Sunday, August 8th, 2021 at 1:51 AM, Adrian Klaver wrote: > 1. Get rid of the first local line . > 2. Then for the remaining local line below change peer to trust and > > restart Postgres. Thank you, but repeat error occurred: sudo sudo service postgresql restart [ ok ] Restarting P

Re: (13.1) pg_basebackups ./. pg_verifybackup

generated by the server > at the time of the backup. The backup must be stored in the "plain" format; > a "tar" format backup can be checked after extracting it." I've studied now the fine docs again and have some additional questions. The backup was done fine t