Re: [External] Re: md5 issues Postgres14 on OL7

2021-12-22 Thread Michael Mühlbeyer
thanks Christoph, best, Michael -Original Message- From: Christoph Moench-Tegeder Date: Monday, 20. December 2021 at 15:22 To: Michael Mühlbeyer Cc: "pgsql-general@lists.postgresql.org" Subject: [External] Re: md5 issues Postgres14 on OL7 Hi! ## Michael Mühlbeyer

Re: Packages, inner subprograms, and parameterizable anonymous blocks for PL/pgSQL

2021-12-22 Thread Pavel Stehule
> > From PostgreSQL's SQL perspective the session variables are common > database objects (contra SQL/PL where package variables are SQL/PL language > objects), and SQL disallows ambiguity. This is a little bit more complex > problem, because session variables can be used everywhere in Postgres

Re: Packages, inner subprograms, and parameterizable anonymous blocks for PL/pgSQL

2021-12-22 Thread Pavel Stehule
Hi Yes, I did read your “schema variables” post on your site “Pavel Stehule’s > blog — Some notes about PostgreSQL”. It gives me a very good idea about > what you have in mind. > > But as I’ve come to understand the term “Functional Spec”, this denotes a > formal deliverable that a product

Re: Packages, inner subprograms, and parameterizable anonymous blocks for PL/pgSQL

2021-12-22 Thread Bryn Llewellyn
> david.g.johns...@gmail.com wrote: > >> b...@yugabyte.com wrote: >> >> update t set t.v = p.v where t.k = p.k; >> >> At run-time, p() terminates with an obscurely worded error: >> >> 42703: column "t" of relation "t" does not exist. > > "set t.v" is simply invalid SQL and the error has

Re: Packages, inner subprograms, and parameterizable anonymous blocks for PL/pgSQL

2021-12-22 Thread David G. Johnston
On Wed, Dec 22, 2021 at 6:27 PM Bryn Llewellyn wrote: > > * update t set t.v = p.v where t.k = p.k;* > At run-time, p() terminates with an obscurely worded error: > > 42703: column "t" of relation "t" does not exist. > > "set t.v" is simply invalid SQL and the error has nothing with this

Re: Packages, inner subprograms, and parameterizable anonymous blocks for PL/pgSQL

2021-12-22 Thread Bryn Llewellyn
> david.g.johns...@gmail.com wrote: > >> b...@yugabyte.com wrote: >> >> Is this model not used for the PostgreSQL system? > > It is not. Basically we have an "Proposed Patches" tracker and they either > get committed, or they do

Re: Packages, inner subprograms, and parameterizable anonymous blocks for PL/pgSQL

2021-12-22 Thread Bryn Llewellyn
> david.g.johns...@gmail.com wrote: > >> b...@yugabyte.com wrote: >> >> Is this model not used for the PostgreSQL system? > > It is not. Basically we have an "Proposed Patches" tracker and they either > get committed, or they do not. Once committed, new features become available > at the

Re: Tab-completion error...?

2021-12-22 Thread Adrian Klaver
On 12/22/21 2:14 PM, Theodore M Rolle, Jr. wrote: Please reply to list also. Ccing list. From below, what did pacman -Syyuu do? You are correct in guessing what I did... config.log: a bunch of #define HAVE_LIBREADLINE 1 then configure:13450: checking readline/readline.h usability

Re: Tab-completion error...?

2021-12-22 Thread Magnus Hagander
On Wed, Dec 22, 2021 at 10:16 PM Theodore M Rolle, Jr. wrote: > I'm having a problem with v14.1 on my Raspberry Pi 4[8Gb] > After a clean download and compile, when using psql, using tab completion > psql -U postgres > postgres=# \i my_databases\tpsql: symbol lookup error: psql: undefined >

Re: Tab-completion error...?

2021-12-22 Thread Adrian Klaver
On 12/22/21 1:15 PM, Theodore M Rolle, Jr. wrote: I'm having a problem with v14.1 on my Raspberry Pi 4[8Gb] After a clean download and compile, when using psql, using tab completion psql -U postgres postgres=# \i my_databases\tpsql: symbol lookup error: psql: undefined symbol: PQmblenBounded

Re: Packages, inner subprograms, and parameterizable anonymous blocks for PL/pgSQL

2021-12-22 Thread David G. Johnston
On Wed, Dec 22, 2021 at 1:54 PM Bryn Llewellyn wrote: > > Is this model not used for the PostgreSQL system? > It is not. Basically we have an "Proposed Patches" tracker and they either get committed, or they do not. Once committed, new features become available at the next annual release. >

Tab-completion error...?

2021-12-22 Thread Theodore M Rolle, Jr.
I'm having a problem with v14.1 on my Raspberry Pi 4[8Gb] After a clean download and compile, when using psql, using tab completion psql -U postgres postgres=# \i my_databases\tpsql: symbol lookup error: psql: undefined symbol: PQmblenBounded

Re: Packages, inner subprograms, and parameterizable anonymous blocks for PL/pgSQL

2021-12-22 Thread Bryn Llewellyn
> pavel.steh...@gmail.com wrote: > >> b...@yugabyte.com wrote: >> >>> pavel.steh...@gmail.com wrote: >>> b...@yugabyte.com wrote: I’m still hoping that I might get some pointers to whitepapers or blog posts that expand on those bullets that I quoted from the PG doc:

Re: surprisingly slow creation of gist index used in exclude constraint

2021-12-22 Thread Laurenz Albe
On Wed, 2021-12-22 at 09:58 +, Chris Withers wrote: > A year and a half later, now that version 14 is the latest available, > I wonder if anything has changed with respect to gist index creation? > Probably also worth asking: are there now different index types this > application should be

Re: Postgresql crashing during pg_dump

2021-12-22 Thread Ron
On 12/22/21 8:40 AM, Tom Lane wrote: Paulo Silva writes: I have a huge table with 141456059 records on a PostgreSQL 10.18 database. When I try to do a pg_dump on that table, postgresql gives a segfault, displaying this message: 2021-12-22 14:08:03.437 UTC [15267] LOG: server process (PID

Re: Postgresql crashing during pg_dump

2021-12-22 Thread Tom Lane
Paulo Silva writes: > I have a huge table with 141456059 records on a PostgreSQL 10.18 database. > When I try to do a pg_dump on that table, postgresql gives a segfault, > displaying this message: > 2021-12-22 14:08:03.437 UTC [15267] LOG: server process (PID 25854) was > terminated by signal

Postgresql crashing during pg_dump

2021-12-22 Thread Paulo Silva
Hello, I have a huge table with 141456059 records on a PostgreSQL 10.18 database. When I try to do a pg_dump on that table, postgresql gives a segfault, displaying this message: 2021-12-22 14:08:03.437 UTC [15267] LOG: server process (PID 25854) was terminated by signal 11: Segmentation fault

Re: surprisingly slow creation of gist index used in exclude constraint

2021-12-22 Thread Chris Withers
Hi, A year and a half later, now that version 14 is the latest available, I wonder if anything has changed with respect to gist index creation? Probably also worth asking: are there now different index types this application should be using? cheers,