Re: walreceiver fails on asynchronous replica [SEC=UNOFFICIAL]

2024-02-26 Thread Kyotaro Horiguchi
At Fri, 23 Feb 2024 04:04:03 +, Mark Schloss wrote in > <2024-02-23 07:50:05.637 AEDT [1957121]: [1-1] user=,db= > LOG: started > streaming WAL from primary at 6/B000 on timeline 5 > <2024-02-23 07:50:05.696 AEDT [1957117]: [6-1] user=,db= > LOG: invalid > magic number in log se

Re: Fastest way to clone schema ~1000x

2024-02-26 Thread Emiel Mols
We've experimented with shared buffers to no effect. The 2048 we actually need for our test setup. The way this works is that we have a single preforked backend for all tests where each backend worker maintains persistent connections *per test* (in database-per-test), so with say 50 backend proces

Re: Fastest way to clone schema ~1000x

2024-02-26 Thread Daniel Gustafsson
> On 26 Feb 2024, at 09:46, Emiel Mols wrote: > The 2048 we actually need for our test setup. There is a measurable overhead in connections, regardless of if they are used or not. If you are looking to squeeze out performance then doing more over already established connections, and reducing ma

Re: Fastest way to clone schema ~1000x

2024-02-26 Thread Emiel Mols
On Mon, Feb 26, 2024 at 3:50 PM Daniel Gustafsson wrote: > There is a measurable overhead in connections, regardless of if they are > used > or not. If you are looking to squeeze out performance then doing more over > already established connections, and reducing max_connections, is a good > pla

Re: Performance issue debugging

2024-02-26 Thread veem v
On Fri, 23 Feb, 2024, 2:54 am Vick Khera, wrote: > On Thu, Feb 22, 2024 at 4:03 PM veem v wrote: > >> Hi All, >> As i understand we have pg_stats_activity which shows the real time >> activity of sessions currently running in the database. And the >> pg_stats_statement provides the aggregated in

Clarity regarding the procedures call in postgresql for public and non-public schema

2024-02-26 Thread Sasmit Utkarsh
Hi Postgresql Team, ***Facing the below issue, while calling the below procedures in public and non-public schema *shc* for ( *shc_uadmin* user) [shc_user@cucmtpccu1 ~]$ export PGHOST= cucmpsgsu0.postgres.database.azure.com [shc_user@cucmtpccu1 ~]$ export PGDATABASE=mshcd [shc_user@cucmtpccu1 ~]$

Re: Clarity regarding the procedures call in postgresql for public and non-public schema

2024-02-26 Thread Sasmit Utkarsh
Hello Boris, Please find the below snippets for sql_select_size_procedure /** creation **/ res = PQexec(conn," CREATE OR REPLACE PROCEDURE *sql_select_size_procedure*(hexid text, rtp_in integer, INOUT size_data text ) LANGUAGE plpgsql AS $$ BEGIN SELECT size FROM riat WHER

could not open file "global/pg_filenode.map": Operation not permitted

2024-02-26 Thread Nick Renders
Hello, We have a Postgres server that intermittently logs the following: 2024-02-26 10:29:41.580 CET [63962] FATAL: could not open file "global/pg_filenode.map": Operation not permitted 2024-02-26 10:30:11.147 CET [90610] LOG: could not open file "postmaster.pid": Operation not permitted; con

Re: could not open file "global/pg_filenode.map": Operation not permitted

2024-02-26 Thread Laurenz Albe
On Mon, 2024-02-26 at 15:14 +0100, Nick Renders wrote: > We have a Postgres server that intermittently logs the following: > > 2024-02-26 10:29:41.580 CET [63962] FATAL:  could not open file > "global/pg_filenode.map": Operation not permitted > 2024-02-26 10:30:11.147 CET [90610] LOG:  could not

pPL/pgSQL restriction on characters for copying types?

2024-02-26 Thread Thiemo Kellner
Hi My names can contain a special character (⠒), e.g. to separate the donator object from the name or the name from the type. Typically, I use this with foreign keys, e.g. table PARENT has the surrogate key ID, the table CHILD would then have the column PARENT⠒ID. That way, I can use the unde

Postgres > 12 with Windows Server 2012

2024-02-26 Thread Markus Oley
Hello everyone, I need to run Postgres on Windows Server 2012. Postgres 12 is EndOfLive in < 12 months, so I'd like to use newer versions (I've got Postgres 15 sorted) in this scenario. However, I have concerns because Postgres 13 onwards is no longer specified for Windows Server 2012. Is this just

Re: pPL/pgSQL restriction on characters for copying types?

2024-02-26 Thread Thiemo Kellner
Oh, I totally forgot to mention that I ran the scripts with DbVisualizer against a 16.1 (Debian 16.1-1.pgdg110+1) server using PostgreSQL JDBC Driver 42.6.0 . Am 26.02.2024 um 16:51 schrieb Thiemo Kellner: Hi My names can contain a special character (⠒), e.g. to separate the donator object f

Re: Fastest way to clone schema ~1000x

2024-02-26 Thread Adrian Klaver
On 2/26/24 01:06, Emiel Mols wrote: On Mon, Feb 26, 2024 at 3:50 PM Daniel Gustafsson > wrote: There is a measurable overhead in connections, regardless of if they are used or not.  If you are looking to squeeze out performance then doing more over alr

Re: Clarity regarding the procedures call in postgresql for public and non-public schema

2024-02-26 Thread Adrian Klaver
On 2/26/24 04:26, Sasmit Utkarsh wrote: Hi Postgresql Team, ***Facing the below issue, while calling the below procedures in public and non-public schema *shc* for ( *shc_uadmin* user) *<3>0164503{----.noterm}-[ERROR] PREPARE failed for RIAT! ERROR:  procedu

Re: pPL/pgSQL restriction on characters for copying types?

2024-02-26 Thread Tom Lane
Thiemo Kellner writes: > However, I want to create a (trigger) function to impose data > consistency. For that purpose, I try to copy the data type of a PL/pgSQL > variable from the base object, a view in that case. Trying so, I get the > following error on installation of the function. > V⠒NO

Re: Clarity regarding the procedures call in postgresql for public and non-public schema

2024-02-26 Thread Tom Lane
Adrian Klaver writes: > On 2/26/24 04:26, Sasmit Utkarsh wrote: >> ***Facing the below issue, while calling the below procedures in public >> and non-public schema *shc* for ( *shc_uadmin* user) > 1) From the error message: > "ERROR: procedure sql_select_size_procedure(text, > integer, unknown

Re: pPL/pgSQL restriction on characters for copying types?

2024-02-26 Thread Thiemo Kellner
Thanks for the hint and care. The install script has a set statement already and I now added the search_path clause to no avail. Please find the entire code attached and a screenshot from the error. Am 26.02.2024 um 17:35 schrieb Tom Lane: Thiemo Kellner writes: However, I want to create a (

Re: pPL/pgSQL restriction on characters for copying types?

2024-02-26 Thread Adrian Klaver
On 2/26/24 08:53, Thiemo Kellner wrote: Thanks for the hint and care. The install script has a set statement already and I now added the search_path clause to no avail. Please find the entire code attached and a screenshot from the error. I quick test: create table type_test(NODE_TYPE⠒NAME te

Re: pPL/pgSQL restriction on characters for copying types?

2024-02-26 Thread Thiemo Kellner
Shame on me. My bad. It was the order of installation that did not work. Sorry for that. I was mislead by the error message. If an object is missing I would not expect an invalid type name message. Thanks Am 26.02.2024 um 17:53 schrieb Thiemo Kellner: Thanks for the hint and care. The install

Re: pPL/pgSQL restriction on characters for copying types?

2024-02-26 Thread Adrian Klaver
On 2/26/24 09:30, Thiemo Kellner wrote: Shame on me. My bad. It was the order of installation that did not work. Sorry for that. I was mislead by the error message. If an object is missing I would not expect an invalid type name message. For all the code knows it could be just a misspelling.

Re: pPL/pgSQL restriction on characters for copying types?

2024-02-26 Thread Tom Lane
Adrian Klaver writes: > On 2/26/24 09:30, Thiemo Kellner wrote: >> Shame on me. My bad. It was the order of installation that did not work. >> Sorry for that. I was mislead by the error message. If an object is >> missing I would not expect an invalid type name message. > For all the code knows

Re: Unable to get PostgreSQL 15 with Kerberos (GSS) working

2024-02-26 Thread Stephen Frost
Greetings, * Matthew Dennison (m...@matty-uk.co.uk) wrote: > No matter what I try I don't seem to be able to get the psl command locally > to work using Kerberos. I receive for following message: > FATAL: GSSAPI authentication failed for user "postgres" > FATAL: GSSAPI authentication failed fo