Re: How to get debuginfo from building source code

2020年10月22日(木) 11:51 Hou, Zhijie : > > Hi > > My PostgreSQL 10.3 in Centos7.4 exited abnormally and generated core.dump. > > I want to analyze the core.dump but I does not find > postgresql10-debuginfo-10.3 in > https://download.postgresql.org/pub/repos/yum/debug/10/redhat/rhel-7.4-x86_64/ > >

How to get debuginfo from building source code

Hi My PostgreSQL 10.3 in Centos7.4 exited abnormally and generated core.dump. I want to analyze the core.dump but I does not find postgresql10-debuginfo-10.3 in https://download.postgresql.org/pub/repos/yum/debug/10/redhat/rhel-7.4-x86_64/ Can I get the debuginfo from building the source code

Re: json_to_recordset() and CTE performance

PostgreSQL 13.0. You’d have to be specific about the configs you’re looking for, I’m using Postgres.app (postgresapp.com ) and am uncertain if it’s distributed with non-default configs. But, a quick grep shows these items that are configured: max_wal_size = 1GB

Re: json_to_recordset() and CTE performance

Version? What is the value for work_mem and other configs that are non-default? I see some estimates that are rather off like - -> Nested Loop (cost=0.26..4.76 rows=100 width=148) (actual time=183.906..388716.550 rows=8935 loops=1) Buffers: shared hit=53877

Re: using psql 11.4 with a server 13.0 && meta commands

W dniu 2020-10-21 o 13:54, Matthias Apitz pisze: Hello, I've found the following problem using psql 11.4 against a server 13.0: you may install a separate 13.0 psql binary and use that one against the 13.0 server

Re: temp table same name real table

Moving this over to -hackers and the commitfest https://www.postgresql.org/message-id/CAKFQuwaZjsaQ9KdDKjcwgGo3axg2t0BdBVYJiHf%3DH9nbvsxQbQ%40mail.gmail.com David J. On Thu, Oct 1, 2020 at 5:14 PM David G. Johnston wrote: > On Wed, Sep 30, 2020 at 7:41 AM Tom Lane wrote: > >> If you really

json_to_recordset() and CTE performance

Hello, I’ve written an sql function that takes a single JSON parameter, in this case an array of objects each with eight properties (example below.) This function uses json_to_recordset() in a CTE to insert three rows on two tables. It takes nearly 7 minutes to insert my dataset of 8935

Re: using psql 11.4 with a server 13.0 && meta commands

On 10/21/20 4:54 AM, Matthias Apitz wrote: Hello, I've found the following problem using psql 11.4 against a server 13.0: $ export LANG=en_US.UTF-8 $ psql -Usisis -dsisis psql (11.4, server 13.0) WARNING: psql major version 11, server major version 13. Some psql features might not

Re: using psql 11.4 with a server 13.0 && meta commands

2020年10月21日(水) 20:54 Matthias Apitz : > > > Hello, > > I've found the following problem using psql 11.4 against a server 13.0: > > $ export LANG=en_US.UTF-8 > $ psql -Usisis -dsisis > psql (11.4, server 13.0) > WARNING: psql major version 11, server major version 13. > Some psql features

using psql 11.4 with a server 13.0 && meta commands

Hello, I've found the following problem using psql 11.4 against a server 13.0: $ export LANG=en_US.UTF-8 $ psql -Usisis -dsisis psql (11.4, server 13.0) WARNING: psql major version 11, server major version 13. Some psql features might not work. Type "help" for help. sisis=# \d

Re: Pgpool2 Service Won't Start

Hi Bo, I replaced the pgpool.conf file with the original file, reconfigured and it works now. Interesting because it was pretty much the same settings after reconfiguring again. Must be a setting that I missed. Thanks, Alan Bo Peng wrote > Hi, > > On Fri, 16 Oct 2020 14:33:33 -0700 (MST) >

RUM and WAL-generation

Hi all. The RUM-index is very nice, but indexes get very large and produce insane amounts of WAL. Due to the way PG works (IIUC), updating an int-column in a row produces lots of WAL because the whole row is duplicated, and if that row holds RUM-indexed columns it gets really bad... We hav

Re: rum index supported on pg13?

excellent. pg13+rum passes all our tests. thanks-john On Thu, Oct 15, 2020 at 3:18 AM Teodor Sigaev wrote: > > Done, thank you > > On 14.10.2020 19:30, Devrim Gündüz wrote: > > > > Hi Teodor, > > > > On Wed, 2020-10-14 at 18:49 +0300, Teodor Sigaev wrote: > >> Thank you, fixed and published. >