'trusted'/'untrusted' PL in DoD/DISA PostgreSQL STIGs

2024-05-05 Thread Chapman Flack
Hi hackers, More or less by chance, I stumbled on a Security Technical Implementation Guide (STIG, promulgated by the US Dept. of Defense, Defense Information Systems Agency) for PostgreSQL (specific to PG 9.x, so a bit dated). There is a rule in the STIG that pertains to PLs, and seems to get ba

Re: 'trusted'/'untrusted' PL in DoD/DISA PostgreSQL STIGs

2024-05-05 Thread Joe Conway
On 5/5/24 13:53, Chapman Flack wrote: The four STIGs suggest the same email address [5] for comments or proposed revisions. I could send these comments there myself, but I thought it likely that others in the community have already been involved in the development of those documents and might hav

Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements

2024-05-05 Thread Michail Nikolaev
Hello, Matthias! I just realized there is a much simpler and safe way to deal with the problem. So, d9d076222f5b94a85e0e318339cfc44b8f26022d(1) had a bug because the scan was not protected by a snapshot. At the same time, we want this snapshot to affect not all the relations, but only a subset of

Re: Weird test mixup

2024-05-05 Thread Michael Paquier
On Thu, May 02, 2024 at 12:35:55PM -0700, Noah Misch wrote: > I should have given a simpler example: > > s1: local-attach to POINT > s2: enter InjectionPointRun(POINT), yield CPU just before injection_callback() > s1: exit > s2: wake up and run POINT as though it had been non-local Hmm. Even if

Re: 039_end_of_wal: error in "xl_tot_len zero" test

2024-05-05 Thread Thomas Munro
On Thu, Feb 15, 2024 at 10:40 PM Anton Voloshin wrote: > On 19/01/2024 01:35, Thomas Munro wrote: > > I don't yet have an opinion on the best way to > > do it though. Would it be enough to add emit_message($node, 0) after > > advance_out_of_record_splitting_zone()? > > Yes, indeed that seems to b

Re: SQL:2011 application time

2024-05-05 Thread jian he
On Wed, May 1, 2024 at 12:39 AM Paul Jungwirth wrote: > > On 4/30/24 09:24, Robert Haas wrote: > > Peter, could you have a look at > > http://postgr.es/m/47550967-260b-4180-9791-b224859fe...@illuminatedcomputing.com > > and express an opinion about whether each of those proposals are (a) > > good

Re: 039_end_of_wal: error in "xl_tot_len zero" test

2024-05-05 Thread Tom Lane
Thomas Munro writes: > Oh, it looks like this new build farm animal "skimmer" might be > reminding us about this issue: > https://buildfarm.postgresql.org/cgi-bin/show_history.pl?nm=skimmer&br=HEAD > I don't know why it changed, At this point it seems indisputable that 7d2c7f08d9 is what broke sk

Re: Help update PostgreSQL 13.12 to 13.14

2024-05-05 Thread Kashif Zeeshan
Hi Upgrade works when you have an existing Postgres installation with server running. If you run the following command then it will upgrade the existing installation of postgre. sudo dnf install -y postgresql13-server But you don't need to execute the below commands as this will create data direc

Re: Documentation to upgrade logical replication cluster

2024-05-05 Thread vignesh C
On Fri, 23 Feb 2024 at 04:58, Peter Smith wrote: > > Hi Vignesh, I have no further comments. Patch v9 LGTM. The v9 version patch was not applying on top of HEAD because of few commits, the updated v10 version patch is rebased on top of HEAD. Regards, Vignesh From 0850792d2d52368af9a54698c03543b4

Re: psql: fix variable existence tab completion

2024-05-05 Thread Anton A. Melnikov
Hello! On 14.03.2024 17:57, Alexander Korotkov wrote: On Sun, Mar 3, 2024 at 5:37 PM Erik Wienhold wrote: On 2024-03-03 03:00 +0100, Steve Chavez wrote: psql has the :{?name} syntax for testing a psql variable existence. But currently doing \echo :{?VERB doesn't trigger tab completion. This