Re: Proposed Japanese Translation of Code of Conduct Policy

> The PostgreSQL Community Code of Conduct Committee has received a draft of > the Japanese translation of the Code of Conduct Policy for review. > The enclosed draft contains the "Licence" section that was added into the > CoC in the Japanese version and other fixes to align with the English > ver

Re: deb http://apt.postgresql.org/pub/repos/apt/ bookworm-pgdg main 15

On 5/11/25 14:22, Andrej wrote: Hi Adrian, May 8th a round of new releases where made: https://www.postgresql.org/about/news/postgresql-175-169-1513-1418-and-1321-released-3072/ I see ...

Re: deb http://apt.postgresql.org/pub/repos/apt/ bookworm-pgdg main 15

Hi Adrian, Thank you for the super-quick response! > > We have two clusters of postgres running, and a couple of machines have > > local postgres databases installed via ansible, using ANXS.postgresql. > > This has been working fine for years, installing varied versions of > > postgres, doing

Re: deb http://apt.postgresql.org/pub/repos/apt/ bookworm-pgdg main 15

On 5/11/25 13:59, Andrej wrote: Hi, We have two clusters of postgres running, and a couple of machines have local postgres databases installed via ansible, using ANXS.postgresql. This has been working fine for years, installing varied versions of postgres, doing upgrades & migrations without

deb http://apt.postgresql.org/pub/repos/apt/ bookworm-pgdg main 15

Hi, We have two clusters of postgres running, and a couple of machines have local postgres databases installed via ansible, using ANXS.postgresql. This has been working fine for years, installing varied versions of postgres, doing upgrades & migrations without a hitch. Since last week we're seein

Re: Updating to PostgreSQL 17.5

Hi Tom, > On 11 May 2025, at 21:36, Tom Lane wrote: > > Sorry --- it means BRIN indexes that use one of the "xxx_bloom_ops" opclasses. > > https://www.postgresql.org/docs/current/brin.html#BRIN-BUILTIN-OPCLASSES Ah, so that'd reduce my monster query to: select concat ('reindex index "', s

Re: Updating to PostgreSQL 17.5

Paul Foerster writes: > the release notes for PostgreSQL 17.5 > (https://www.postgresql.org/docs/17/release-17-5.html) state: > "Also, if you have any BRIN bloom indexes, it may be advisable to reindex > them after updating." > I don't know what exactly that means. Sorry --- it means BRIN inde

Updating to PostgreSQL 17.5

Hi, the release notes for PostgreSQL 17.5 (https://www.postgresql.org/docs/17/release-17-5.html) state: "Also, if you have any BRIN bloom indexes, it may be advisable to reindex them after updating." I don't know what exactly that means. So I read about BRIN and BLOOM indexes and learned how

Re: 回复: are the 2 if-statements in join_is_legal() removable?

g l writes: > Then I run the core regression tests with "make installcheck-parallel > " for v18beta1 as the document dictates. When the regression test is done, > only the last 2 log entries are found in logfile, the first 2 entries are not > printed at all. I run core regression also with v14.1

Re: Postgresql 18beta1 and SPI changes

Achilleas Mantzios writes: > We use are own version of DBmirror, we run our replication in a highly > fine grained manner. So every upgrade I have to make the code compile > and test. Up to PostgreSQL 17, I only got minor compilation problems > that I managed to resolve fairly easily. However t

Postgresql 18beta1 and SPI changes

Dear members We use are own version of DBmirror, we run our replication in a highly fine grained manner. So every upgrade I have to make the code compile and test. Up to PostgreSQL 17, I only got minor compilation problems that I managed to resolve fairly easily. However this didn't prove to b

回复: are the 2 if-statements in join_is_legal() removable?

Hi Tom: Thanks for your reply! I add logs like this: if (bms_is_subset(sjinfo->min_lefthand, rel1->relids) &&   bms_is_subset(sjinfo->min_righthand, rel2->relids)) {   if (match_sjinfo) { elog(LOG, "gunkris111