Re: Error while updating a table

On 2025-04-19 13:06:27 +, sivapostg...@yahoo.com wrote: > Thanks Laurenz, > > it is 100% clear that an earlier statement in the same transaction must > > have got an error. Write your application so that it logs *every* error > > that comes from the database, then you are sure to catch that er

Re: Error while updating a table

On Sat, Apr 19, 2025 at 6:06 AM sivapostg...@yahoo.com < sivapostg...@yahoo.com> wrote: > By any chance, if I get that statement, what should I do? > Read it. What are the Steps (or documentation) to correct this issue? > > Impossible to say until the statement is read. David J.

Re: Error while updating a table

Thanks Laurenz, > it is 100% clear that an earlier statement in the same transaction musthave >got an error.  Write your application so that it logs *every* error that comes from the database, then you are sure to catch that error. There is an option to log every sql statement that's executed fr

Re: Error while updating a table

On Sat, 2025-04-19 at 12:38 +, sivapostg...@yahoo.com wrote: > So far, I couldn't find the query that caused the error.   Is there any way > to unlock it?   > > Re-start, Format and fresh install of windows, etc. ? On Windows you have to reboot, bow three times toward sunset, say a prayer to

Re: Error while updating a table

So far, I couldn't find the query that caused the error.   Is there any way to unlock it?   Re-start, Format and fresh install of windows, etc. ? Happiness Always BKR Sivaprakash On Friday 18 April, 2025 at 04:50:52 pm IST, sivapostg...@yahoo.com wrote: If the query caused an error ..

Re: Error while updating a table

If the query caused an error Does it mean that other reasons might also be there? Nevertheless, I'll check the log file to find the query... Happiness Always BKR Sivaprakash On Friday 18 April, 2025 at 03:53:06 pm IST, Laurenz Albe wrote: On Fri, 2025-04-18 at 07:31 +, sivapost

Re: Error while updating a table

On Fri, 2025-04-18 at 07:31 +, sivapostg...@yahoo.com wrote: > For the second part, how to identify that culprit query? If the query caused an error, and you left "log_min_messages" at the default setting, the error and the statement that caused it should be in the PostgreSQL log. Yours, Laur

Re: Error while updating a table

Thanks Laurenz, Now I need to do 2 things. 1.  Correct my application to catch errors and do either Rollback or commit.    This part is running smoothly from all other computers, so far.  Nevertheless I'll check that for any missing catch.2.  Find the faulty entry and do rectify. For the second p

Re: Error while updating a table

On Fri, 2025-04-18 at 05:49 +, sivapostg...@yahoo.com wrote: > We use PowerBuilder along with PostgreSQL. > > PostgreSQL 15.7 (Ubuntu 15.7-1.pgdg24.04+1) on x86_64-pc-linux-gnu, compiled > by gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0, 64-bit > > Suddenly, one system starts throwing an error while

Re: Error while updating a table

Hello, We use PowerBuilder along with PostgreSQL. PostgreSQL 15.7 (Ubuntu 15.7-1.pgdg24.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0, 64-bit Suddenly, one system starts throwing an error while updating a record from PowerBuilder.  The same update statement (wind

Re: ERROR: could not read block 0 in file when creating an index out of a function

Luca Ferrari writes: > On Wed, Mar 12, 2025 at 12:54 PM Artur Zakirov wrote: >> In your case `base/357283/365810` file is a new index file. For some >> reason Postgres tries to read the new index. I suppose this is because >> during reading the table `t` within the function `f_t` it tries to >> a

Re: ERROR: could not read block 0 in file when creating an index out of a function

On 3/12/25 14:31, Luca Ferrari wrote: On Wed, Mar 12, 2025 at 12:54 PM Artur Zakirov wrote: I can reproduce this with the table `t` on PG 15.10. I didn't mention I'm running 16.6, but I'm pretty sure it is reproducible on other versions too. In your case `base/357283/365810` file is a new in

Re: ERROR: could not read block 0 in file when creating an index out of a function

On Wed, Mar 12, 2025 at 12:54 PM Artur Zakirov wrote: > > I can reproduce this with the table `t` on PG 15.10. I didn't mention I'm running 16.6, but I'm pretty sure it is reproducible on other versions too. > > In your case `base/357283/365810` file is a new index file. For some > reason Postgr

Re: ERROR: could not read block 0 in file when creating an index out of a function

Hey, On Wed, 12 Mar 2025 at 10:11, Luca Ferrari wrote: > Now, according to the documentation, the function f_t is immutable > since it is not modifying the database, so what is going on? And why > is the same function working if the table has not the constraint on > the column? I can reproduce t

Re: Error on query execution

Igor Korot writes: > On Tue, Mar 4, 2025 at 8:37 PM Tom Lane wrote: >> ... but given that you didn't specify any data type, I think the >> parser will fall back to assuming that $1 is the same type as >> "abf_type", whatever that is. Passing data in binary is not at all >> forgiving about gettin

Re: Error on query execution

H, On Tue, Mar 4, 2025 at 8:37 PM Tom Lane wrote: > > Igor Korot writes: > > binaryIntVal = htonl( (uint32_t) type ); > > paramValues[0] = (char *) &binaryIntVal; > > paramLengths[0] = sizeof( binaryIntVal ); > > paramFormats[0] = 1; > > You're apparently trying to pass this para

Re: Error on query execution

Tom, On Tue, Mar 4, 2025, 8:37 PM Tom Lane wrote: > Igor Korot writes: > > binaryIntVal = htonl( (uint32_t) type ); > > paramValues[0] = (char *) &binaryIntVal; > > paramLengths[0] = sizeof( binaryIntVal ); > > paramFormats[0] = 1; > > You're apparently trying to pass this param

Re: Error on query execution

Hi, Tom, On Tue, Mar 4, 2025 at 8:37 PM Tom Lane wrote: > > Igor Korot writes: > > binaryIntVal = htonl( (uint32_t) type ); > > paramValues[0] = (char *) &binaryIntVal; > > paramLengths[0] = sizeof( binaryIntVal ); > > paramFormats[0] = 1; > > You're apparently trying to pass thi

Re: Error on query execution

Igor Korot writes: > binaryIntVal = htonl( (uint32_t) type ); > paramValues[0] = (char *) &binaryIntVal; > paramLengths[0] = sizeof( binaryIntVal ); > paramFormats[0] = 1; You're apparently trying to pass this parameter as an int4 ... > res = PQexecParams( m_db, "SELECT * FRO

Re: Error on the query

Hi, Pavel, On Tue, Mar 4, 2025 at 11:36 AM Pavel Stehule wrote: > > Hi > > út 4. 3. 2025 v 18:30 odesílatel Igor Korot napsal: >> >> Hi, ALL, >> Trying to execute following query: >> >> [code] >> queries.push_back( L"DO $$ BEGIN IF NOT EXISTS( SELECT 1 FROM >> pg_class c, pg_namespace n

Re: Error on the query

On Tuesday, March 4, 2025, Igor Korot wrote: > > [code] > queries.push_back( L"DO $$ BEGIN IF NOT EXISTS( SELECT 1 FROM > pg_class c, pg_namespace n WHERE n.oid = c.relnamespace AND c.relname > = \'abcatc_x\' AND n.nspname = \'public\' ) THEN CREATE UNIQUE INDEX > \"abcatc_x\" ON \"abcatco

Re: Error on the query

Hi út 4. 3. 2025 v 18:30 odesílatel Igor Korot napsal: > Hi, ALL, > Trying to execute following query: > > [code] > queries.push_back( L"DO $$ BEGIN IF NOT EXISTS( SELECT 1 FROM > pg_class c, pg_namespace n WHERE n.oid = c.relnamespace AND c.relname > = \'abcatc_x\' AND n.nspname = \'pub

Re: ERROR: stack depth limit exceeded

On Wed, 2025-02-19 at 16:49 +0100, Csányi Pál wrote: > the trigger function definition is like: > [...] > INSERT INTO >     HAVONKENTI_MEGTAKARITASAINK (EZEN_IDOKOZBEN, MEGTAKARITVA_RSD, KELT) > [...] > > and the trigger definition is like: > CREATE OR REPLACE TRIGGER uj_nyugdij_beirasakor_kiold >

Re: ERROR: stack depth limit exceeded

On Wed, 19 Feb 2025 at 16:49, Csányi Pál wrote: > Indeed I did, the trigger should have been assigned on > javaink_forgalma table, not on havonkenti_megtakaritasaink table. > Actually, this trigger has been assigned on both tables so far, and I > just deleted it from the havonkenti_megtakaritasai

Re: ERROR: stack depth limit exceeded

Sándor Daku ezt írta (időpont: 2025. febr. 19., Sze, 17:09): > > > > On Wed, 19 Feb 2025 at 16:49, Csányi Pál wrote: >> >> Indeed I did, the trigger should have been assigned on >> javaink_forgalma table, not on havonkenti_megtakaritasaink table. >> Actually, this trigger has been assigned on bot

Re: ERROR: stack depth limit exceeded

Laurenz Albe ezt írta (időpont: 2025. febr. 19., Sze, 12:22): > > On Wed, 2025-02-19 at 11:23 +0100, Csányi Pál wrote: > > I am running postgresql 15 on Debian 12 operating system. > > I also installed PgAdmin4 and am using the desktop version of it. > > I have created a trigger function and a tri

Re: ERROR: stack depth limit exceeded

Not related to the main question, but that query could use a little adjustment. Something like: WITH x AS ( select kelt from javaink_forgalma where en_kaptam is true and az_aru_neve = 'nyugdíjam' order by kelt desc limit 2 ) ,y AS (select min(kelt) from x) ,z AS (select max(kelt) from x) INS

Re: ERROR: stack depth limit exceeded

On Wed, 2025-02-19 at 11:23 +0100, Csányi Pál wrote: > I am running postgresql 15 on Debian 12 operating system. > I also installed PgAdmin4 and am using the desktop version of it. > I have created a trigger function and a trigger which will run the > following code, see below. > Before this trigge

Re: ERROR wrong varnullingrels (b 3) (expected (b)) with LEFT JOIN LATERAL and CTE

On Thu, Nov 28, 2024 at 11:35 PM Tom Lane wrote: > I wrote: > > Thanks for the test case! A quick "git bisect" says I broke it at > > cb8e50a4a09fe541e32cd54ea90a97f2924121a1 is the first bad commit > > commit cb8e50a4a09fe541e32cd54ea90a97f2924121a1 > > Author: Tom Lane > > Date: Fri Aug 30

Re: ERROR wrong varnullingrels (b 3) (expected (b)) with LEFT JOIN LATERAL and CTE

I wrote: > Thanks for the test case! A quick "git bisect" says I broke it at > cb8e50a4a09fe541e32cd54ea90a97f2924121a1 is the first bad commit > commit cb8e50a4a09fe541e32cd54ea90a97f2924121a1 > Author: Tom Lane > Date: Fri Aug 30 12:42:12 2024 -0400 > Avoid inserting PlaceHolderVars in ca

Re: ERROR wrong varnullingrels (b 3) (expected (b)) with LEFT JOIN LATERAL and CTE

Bertrand Mamasam writes: > Ok thank you, here is a short version of the query that works before 16.5 > but not in 16.5+ anymore. Thanks for the test case! A quick "git bisect" says I broke it at cb8e50a4a09fe541e32cd54ea90a97f2924121a1 is the first bad commit commit cb8e50a4a09fe541e32cd54ea90a

Re: ERROR wrong varnullingrels (b 3) (expected (b)) with LEFT JOIN LATERAL and CTE

On Thu, Nov 28, 2024 at 5:15 PM Tom Lane wrote: > Bertrand Mamasam writes: > > I get this error in PG16.5, 16.6 and 17 : > > wrong varnullingrels (b 3) (expected (b)) for Var 1/19 > > Please provide a self-contained test case. A fragmentary query > with no underlying tables is useless for inves

Re: ERROR wrong varnullingrels (b 3) (expected (b)) with LEFT JOIN LATERAL and CTE

Bertrand Mamasam writes: > I get this error in PG16.5, 16.6 and 17 : > wrong varnullingrels (b 3) (expected (b)) for Var 1/19 Please provide a self-contained test case. A fragmentary query with no underlying tables is useless for investigation. https://wiki.postgresql.org/wiki/Guide_to_reportin

Re: Error creating materialized view

On Mon, 2024-11-25 at 06:08 +, Shaun Robinson wrote: > I'm currently testing an application with Postgres 17.2 and am getting an > error > when creating a materialized view which works in version 16 and below. The sql > works fine running as a query, but adding the create materialized view bre

Re: Error creating materialized view

Hi David, I've created a basic example which produces the issue for me and the SQL is below. Thanks Shaun create table diagnosisTest ( id serial primary key, icd_code varchar(10) ); create table encounterTest ( id serial primary key, dx1 integer, dx2 integer, dx3 integer, dx4 integer, dx5 inte

Re: Error creating materialized view

On Mon, 25 Nov 2024, 06:08 Shaun Robinson, wrote: > Hi, > > I'm currently testing an application with Postgres 17.2 and am getting an > error when creating a materialized view which works in version 16 and > below. The sql works fine running as a query, but adding the > create materialized view b

Re: Error Building Postgres 17.0 from Source

> On Oct 4, 2024, at 12:34, Tom Lane wrote: > > If so, the difference is that up to v16 we > included prebuilt HTML docs in the tarballs, but as of v17 we don't. > So "make world" now triggers a local docs build where before it > didn't. Ah! That would be it.

Re: Error Building Postgres 17.0 from Source

Christophe Pettus writes: > On Oct 4, 2024, at 12:05, Tom Lane wrote: >> Yeah, that's what it looks like. I'm a bit confused though because >> 16.x should have failed the same way: building our docs without local >> DTDs has failed for well over a year now [1]. > To add confusion to the fire,

Re: Error Building Postgres 17.0 from Source

> On Oct 4, 2024, at 12:05, Tom Lane wrote: > > Yeah, that's what it looks like. I'm a bit confused though because > 16.x should have failed the same way: building our docs without local > DTDs has failed for well over a year now [1]. To add confusion to the fire, I was successfully buildin

Re: Error Building Postgres 17.0 from Source

Christophe Pettus writes: > On Oct 4, 2024, at 09:35, Corbin Cavolt wrote: >> I'm having a problem building Postgres 17.0 from source. I'm able to build >> all the 16.x versions just fine; I'm running into an error specifically with >> version 17.0. > You might try installing the Debian packag

Re: Error Building Postgres 17.0 from Source

> On Oct 4, 2024, at 09:35, Corbin Cavolt wrote: > > Hi, > > I'm having a problem building Postgres 17.0 from source. I'm able to build > all the 16.x versions just fine; I'm running into an error specifically with > version 17.0. I use a devcontainer for development with my own postgres >

Re: ERROR: could not open relation with OID XXXX

Thank you all for your comments. > I would think that the queries in that case would be running as a superuser in order to do the migrations. Users of codd can choose the role that applies their migrations. Codd even supports individual migrations running with ad-hoc users (so that a migration ca

Re: ERROR: could not open relation with OID XXXX

On 8/25/24 08:36, Marcelo Zabani wrote: > we do some special stuff for catalogs That is good to know, thanks! > I believe you could actually lock the pg_class rows for update. Just add FOR UPDATE at the end of the query. Thanks, but I tried that and got "ERROR:  permission denied for table

Re: ERROR: could not open relation with OID XXXX

On 8/25/24 17:36, Marcelo Zabani wrote: >> we do some special stuff for catalogs > > That is good to know, thanks! > >> I believe you could actually lock the pg_class rows for update. Just > add FOR UPDATE at the end of the query. > > Thanks, but I tried that and got "ERROR:  permission denie

Re: ERROR: could not open relation with OID XXXX

> we do some special stuff for catalogs That is good to know, thanks! > I believe you could actually lock the pg_class rows for update. Just add FOR UPDATE at the end of the query. Thanks, but I tried that and got "ERROR: permission denied for table pg_class", even if I try it only for tables t

Re: ERROR: could not open relation with OID XXXX

On 8/25/24 15:42, Marcelo Zabani wrote: > Hi all, > > I can reproduce the error in the subject from time to time when querying > catalog tables while DDL is happening concurrently. Here's a bash script > that reproduces it (not always, you might have to run it many times > until you see ERROR:  co

Re: ERROR: could not open relation with OID XXXX

> What version (including minor number)? On my computer I can reproduce the error with v16.1. At my job I know it's v15 but I can't access it right now so don't know the minor version. In any case, at my job it's much bigger queries we run; I'll elaborate why below. > Just out of curiosity, *WHY*

Re: ERROR: could not open relation with OID XXXX

On Sun, Aug 25, 2024 at 9:42 AM Marcelo Zabani wrote: > Hi all, > > I can reproduce the error in the subject from time to time when querying > catalog tables while DDL is happening concurrently. Here's a bash script > that reproduces it (not always, you might have to run it many times until > you

Re: ERROR: could not attach to dynamic shared area

On Wed, Jun 26, 2024 at 02:43:30PM +, Andrew Longwill wrote: > We’re using Postgresql 15.4 in AWS RDS. Since yesterday we have seen > two occurrences where our PHP application becomes unable to connect > to our RDS replicas. In the application logs we see the error > "FATAL: could not attach to

Re: ERROR: found xmin from before relfrozenxid; MultiXactid does no longer exist -- apparent wraparound

On Fri, May 31, 2024 at 1:25 PM Alanoly Andrews wrote: > Yes, and I know that upgrading the Postgres version is the stock answer > for situations like this. The upgrade is in the works. > *Patching *was the solution. It takes *five minutes*. Here's how I did it (since our RHEL systems are block

Re: ERROR: found xmin from before relfrozenxid; MultiXactid does no longer exist -- apparent wraparound

But I was still interested in what the postgres gurus/programmers/hackers had to say about this event. Regards. Alanoly. From: Thom Brown Sent: May 31, 2024 6:14 AM To: Laurenz Albe Cc: Alanoly Andrews ; pgsql-general@lists.postgresql.org Subject: Re: ERROR:

Re: ERROR: found xmin from before relfrozenxid; MultiXactid does no longer exist -- apparent wraparound

On Fri, May 31, 2024, 09:29 Laurenz Albe wrote: > On Thu, 2024-05-30 at 14:58 +, Alanoly Andrews wrote: > > We have a postgres 10.7 database which reports a number of issues on > user-created > > tables as well as system tables. Most errors are one of the following: > > -- ERROR: found xmin

Re: ERROR: found xmin from before relfrozenxid; MultiXactid does no longer exist -- apparent wraparound

On Thu, 2024-05-30 at 14:58 +, Alanoly Andrews wrote: > We have a postgres 10.7 database which reports a number of issues on > user-created > tables as well as system tables. Most errors are one of the following: > -- ERROR:  found xmin 1888159934 from before relfrozenxid 1998177448 > -- ERROR

Re: error in trigger creation

On 4/21/24 14:21, Tom Lane wrote: Adrian Klaver writes: On 4/21/24 11:20, yudhi s wrote: So in this case i was wondering if "event trigger" can cause any additional threat and thus there is no such privilege like "create trigger" exist in postgres and so it should be treated cautiously? An

Re: error in trigger creation

Adrian Klaver writes: > On 4/21/24 11:20, yudhi s wrote: >> So in this case i was wondering if "event trigger" can cause any >> additional threat and thus there is no such privilege like "create >> trigger" exist in postgres and so it should be treated cautiously? > An event trigger runs as a s

Re: error in trigger creation

On 4/21/24 11:20, yudhi s wrote: On Sun, Apr 21, 2024 at 8:13 PM Tom Lane > wrote: So do you mean , we should not create the event trigger using the "security definer" , rather have the super user do this each time we have to create the event trigger? Actuall

Re: error in trigger creation

On Mon, 22 Apr, 2024, 1:34 am Ron Johnson, wrote: > On Sun, Apr 21, 2024 at 2:58 PM yudhi s > wrote: > >> the partition drop from parent is taking longer as it scans all the >> partitions of the child table >> > > Does the relevant supporting index exist on the child table? > Yes all the child

Re: error in trigger creation

On Sun, Apr 21, 2024 at 2:58 PM yudhi s wrote: > the partition drop from parent is taking longer as it scans all the > partitions of the child table > Does the relevant supporting index exist on the child table?

Re: error in trigger creation

On Mon, Apr 22, 2024 at 12:02 AM David G. Johnston < david.g.johns...@gmail.com> wrote: > > I suggest you share a script that demonstrates exactly what you are trying > to accomplish. Which event triggers you need to create from the > application and what the functions those triggers call do. > >

Re: error in trigger creation

On Sun, Apr 21, 2024 at 11:20 AM yudhi s wrote: > > On Sun, Apr 21, 2024 at 8:13 PM Tom Lane wrote: > >> "David G. Johnston" writes: >> > On Sunday, April 21, 2024, yudhi s wrote: >> >> Are you saying something like below, in which we first create the >> >> function from super user and then ex

Re: error in trigger creation

On Sun, Apr 21, 2024 at 8:13 PM Tom Lane wrote: > "David G. Johnston" writes: > > On Sunday, April 21, 2024, yudhi s wrote: > >> Are you saying something like below, in which we first create the > >> function from super user and then execute the grant? But doesn't that > mean, > >> each time we

Re: error in trigger creation

On Sun, Apr 21, 2024 at 11:10 AM yudhi s wrote: > > On Sun, Apr 21, 2024 at 7:55 PM David G. Johnston < > david.g.johns...@gmail.com> wrote: > >> On Sunday, April 21, 2024, yudhi s wrote: >> >>> On Sun, Apr 21, 2024 at 1:55 PM David G. Johnston < >>> david.g.johns...@gmail.com> wrote: >>> O

Re: error in trigger creation

On Sun, Apr 21, 2024 at 7:55 PM David G. Johnston < david.g.johns...@gmail.com> wrote: > On Sunday, April 21, 2024, yudhi s wrote: > >> On Sun, Apr 21, 2024 at 1:55 PM David G. Johnston < >> david.g.johns...@gmail.com> wrote: >> >>> On Sunday, April 21, 2024, yudhi s wrote: >>> so that it w

Re: error in trigger creation

"David G. Johnston" writes: > On Sunday, April 21, 2024, yudhi s wrote: >> Are you saying something like below, in which we first create the >> function from super user and then execute the grant? But doesn't that mean, >> each time we want to create a new event trigger we have to be again >> dep

Re: error in trigger creation

On Sunday, April 21, 2024, yudhi s wrote: > On Sun, Apr 21, 2024 at 1:55 PM David G. Johnston < > david.g.johns...@gmail.com> wrote: > >> On Sunday, April 21, 2024, yudhi s wrote: >> >>> so that it will be able to assign the privilege, so we will be able to >>> create the event trigger without n

Re: error in trigger creation

On Sun, Apr 21, 2024 at 1:55 PM David G. Johnston < david.g.johns...@gmail.com> wrote: > On Sunday, April 21, 2024, yudhi s wrote: > >> so that it will be able to assign the privilege, so we will be able to >> create the event trigger without need to run the event trigger script from >> super use

Re: error in trigger creation

On Sunday, April 21, 2024, yudhi s wrote: > so that it will be able to assign the privilege, so we will be able to > create the event trigger without need to run the event trigger script from > super user itself? > Write a security-definer function owned by superuser and grant app_user permissio

Re: Error on create extension pgcrypto. Undefined symbol "EVP_bf_ecb"

> On 7 Feb 2024, at 18:53, Marco Aurelio wrote: > > I changed the path and now the correct version of openssl appears in the > config.log, even so, after recompiling and reinstalling both postgresql and > the pgcrypto contrib, when trying to create the extension in a database I > continue to r

Re: Error on create extension pgcrypto. Undefined symbol "EVP_bf_ecb"

I changed the path and now the correct version of openssl appears in the config.log, even so, after recompiling and reinstalling both postgresql and the pgcrypto contrib, when trying to create the extension in a database I continue to receive the same error, any further suggestions ? Marco Aurélio

Re: Error on create extension pgcrypto. Undefined symbol "EVP_bf_ecb"

Marco Aurelio writes: > I added the include and libraries folders: > --with-libraries=/usr/local/lib --with-includes=/usr/local/include > but configure keeps finding the old version of openssl > configure:14133: checking for openssl > configure:14151: found /usr/bin/openssl > configure:14163: res

Re: Error on create extension pgcrypto. Undefined symbol "EVP_bf_ecb"

I added the include and libraries folders: --with-libraries=/usr/local/lib --with-includes=/usr/local/include but configure keeps finding the old version of openssl configure:14133: checking for openssl configure:14151: found /usr/bin/openssl configure:14163: result: /usr/bin/openssl configure:141

Re: Error on create extension pgcrypto. Undefined symbol "EVP_bf_ecb"

> On 7 Feb 2024, at 15:09, Marco Aurelio wrote: > When I run ./configure I see in config.log that it is always using the base > version of Freebsd. You can use the --with-libraries and --with-includes arguments to ./configure in order to point it to the version you want to build against. -- Da

Re: ERROR: invalid byte sequence for encoding UTF8: 0x00

Laurenz Albe writes: > On Tue, 2024-01-09 at 17:48 +0530, Kiran K V wrote: >> I have a table with bytea column and trying to load the data using copy >> command. >> But Copy command is failing with >> "ERROR: invalid byte sequence for encoding UTF8: 0x00. >> Why postgresql is failing to load when

Re: ERROR: invalid byte sequence for encoding UTF8: 0x00

On Tue, 2024-01-09 at 17:48 +0530, Kiran K V wrote: > I have a table with bytea column and trying to load the data using copy > command. > But Copy command is failing with > "ERROR: invalid byte sequence for encoding UTF8: 0x00. > Why postgresql is failing to load when data contains 0x00. > How to

Re: ERROR: missing chunk number 0 for toast value 1563962066 in pg_toast_2619

On 12/26/23 12:51, Johnathan Tiamoh wrote: Hello, Please, I need help to fix this. Can't do anything in the database. This error keeps popping up. I have tried to do a pg_dump and the same error keeps coming up. You need to provide answers to the questions posed here: https://www.postgresq

Re: ERROR: stack depth limit exceeded

Thank you all for taking the time to help me with my question and offer your advice. Your responses were greatly appreciated! At 2023-09-08 21:53:33, "Tom Lane" wrote: >gzh writes: >> In the Release Notes for PostgreSQL 12.14, we saw the following change: >> https://www.postgre

Re: ERROR: stack depth limit exceeded

gzh writes: > In the Release Notes for PostgreSQL 12.14, we saw the following change: > https://www.postgresql.org/docs/release/12.14/ >> Add recursion and looping defenses in subquery pullup (Tom Lane) >> A contrived query can result in deep recursion and unreasonable amounts of >> time spent

Re: ERROR: stack depth limit exceeded

On Fri, 2023-09-08 at 11:32 +0800, gzh wrote: > I'm sorry I didn't explain the issue clearly.  > Our system is currently running on PostgreSQL 12.13 and we are planning to > upgrade to PostgreSQL 12.16.  > We are currently in the evaluation phase.  > In the Release Notes for PostgreSQL 12.14, we s

Re: ERROR: stack depth limit exceeded

I'm sorry I didn't explain the issue clearly. Our system is currently running on PostgreSQL 12.13 and we are planning to upgrade to PostgreSQL 12.16. We are currently in the evaluation phase. In the Release Notes for PostgreSQL 12.14, we saw the following change: https://www.postgresql.org/

Re: ERROR: stack depth limit exceeded

On Thu, 7 Sept 2023 at 08:45, gzh wrote: > but is there a good way to find out which SQL statements have issues without > having to run all SQL statements, as it would be too expensive? Does your postgresql server log not contain the error with the statement at issue? Geoff

Re: ERROR: stack depth limit exceeded

gzh writes: > I upgraded the version of PostgreSQL from 12.13 to 12.16. > If multiple subqueries or a large number of UNION ALL were used, > the previously unseen error message "ERROR: stack depth limit exceeded" will > appear after upgrading the version. Please provide a self-contained exampl

Re: error: connection to server on socket...

Thank you Adrian. It Worked!!! On 8/1/23 2:55 p.m., Adrian Klaver wrote: On 8/1/23 11:42, Amn Ojee Uw wrote: Ah! Adrean, here is something interesting. /*pg_lsclusters*/ displays the following information /*Ver Cluster Port Status    Owner    Data directory  Log file

Re: error: connection to server on socket...

On 8/1/23 11:42, Amn Ojee Uw wrote: Ah! Adrean, here is something interesting. /*pg_lsclusters*/ displays the following information /*Ver Cluster Port Status    Owner    Data directory  Log file*//* *//*12  main    5432 down,binaries_missing postgres /var/lib/postgresq

Re: error: connection to server on socket...

Ah! Adrean, here is something interesting. /*pg_lsclusters*/ displays the following information /*Ver Cluster Port Status    Owner    Data directory  Log file*//* *//*12  main    5432 down,binaries_missing postgres /var/lib/postgresql/12/main /var/log/postgresql/postgre

Re: error: connection to server on socket...

On 8/1/23 03:22, Amn Ojee Uw wrote: Using the following command on my Debian 12 machine: /*sudo apt-get install postgresql postgresql-15 postgresql-client-common postgresql-common postgresql-contrib postgresql-doc phppgadmin */ and following the instruction on this

Re: error: connection to server on socket...

p...@pfortin.com writes: > On Tue, 1 Aug 2023 06:22:46 -0400 Amn Ojee Uw wrote: >> "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory*//* > Like mine, your distro probably uses /tmp/.s.PGSQL.5432 > $ ll /tmp/.s.PGSQL.5432 > srwxrwxrwx 1 postgres postgres 0 Aug 1 06:33 /tmp/.s.

Re: error: connection to server on socket...

El día martes, agosto 01, 2023 a las 07:28:49 -0400, p...@pfortin.com escribió: > On Tue, 1 Aug 2023 06:22:46 -0400 Amn Ojee Uw wrote: > > >"/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory*//* > > Like mine, your distro probably uses /tmp/.s.PGSQL.5432 > $ ll /tmp/.s.PGSQL.

Re: error: connection to server on socket...

On Tue, 1 Aug 2023 06:22:46 -0400 Amn Ojee Uw wrote: >"/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory*//* Like mine, your distro probably uses /tmp/.s.PGSQL.5432 $ ll /tmp/.s.PGSQL.5432 srwxrwxrwx 1 postgres postgres 0 Aug 1 06:33 /tmp/.s.PGSQL.5432= https://askubuntu.co

Re: error: connection to server on socket...

On 01.08.23 12:22, Amn Ojee Uw wrote: Using the following command on my Debian 12 machine: sudo apt-get install postgresql postgresql-15 postgresql-client-common postgresql-common postgresql-contrib postgresql-doc phppgadmin and following the instruction on this

Re: error: connection to server on socket...

_*Addendum*_ I tried this, but to no avail : /*sudo systemctl start postgresql*/ On 8/1/23 6:22 a.m., Amn Ojee Uw wrote: Using the following command on my Debian 12 machine: /*sudo apt-get install postgresql postgresql-15 postgresql-client-common postgresql-common postgresql-contrib postgre

Re: Error 503 Backend fetch failed

Greetings, * Sabri Taner Burak ALTINDAL (s...@protonmail.com) wrote: > I am interning at a company. I was using Python to download your mail lists, > but it seems that there was an unwanted situation, and you have restricted > access to log in. However, I read that you are not against the storag

Re: error in the example given for numeric data types

On Sat, Jul 15, 2023 at 10:50 AM Priyank Rajvansh < rajvansh.priy...@gmail.com> wrote: > > First of all thanks for your reply.This mean that this was a bug in the > previous versions right? > No, it means that a prior version limitation has been lifted, so a definition that was previously undefin

Re: error in the example given for numeric data types

First of all thanks for your reply.This mean that this was a bug in the previous versions right? Secondly, I would love to connect with you as I am a college student and I want to be a contributor to open source software so can we connect on some platform? I really need someone to guide me Thankin

Re: error in the example given for numeric data types

jian he writes: >> practice=# create table t1(height numeric(3,5)); >> ERROR: NUMERIC scale 5 must be between 0 and precision 3 > it works in pg15, not in pg14. > see my test: https://dbfiddle.uk/wgfjCx7j Indeed. The quoted documentation text is different between v15 and prior versions. Observ

Re: error in the example given for numeric data types

> Page: https://www.postgresql.org/docs/15/datatype-numeric.html "docs/15" means this url pointer to pg version 15. > practice=# create table t1(height numeric(3,5)); > ERROR: NUMERIC scale 5 must be between 0 and precision 3 > LINE 1: create table t1(height numeric(3,5)); > Please look into th

Re: ERROR: only immutable functions supported in continuous aggregate view

Ok, now I understand, thank you. My solution is to create materialized view with intermediate values and the create a normal view on top that uses the intermediate values and the jsonb_build_object function to create the desired result. Kind regards, Martijn de Munnik On 2023-03-11 16:47, To

Re: ERROR: only immutable functions supported in continuous aggregate view

Martijn de Munnik writes: > The error is caused by the jsonb_build_object function, is there any > reason why this function is not IMMUTABLE? It can invoke arbitrary datatype output functions, some of which are not immutable. We unfortunately lack any infrastructure that would allow reasoning th

Re: ERROR: unsupported Unicode escape sequence - in JSON-type column

On 2/28/23 01:17, Erik Wienhold wrote: >> On 27/02/2023 13:13 CET Laurenz Albe wrote: >> >> I'd be curious to know how the customer managed to do that. >> Perhaps there is a loophole in PostgreSQL that needs to be fixed. > Probably via some data access layer and not directly via Postgres. It's ea

Re: ERROR: unsupported Unicode escape sequence - in JSON-type column

On 2/27/23 22:13, Laurenz Albe wrote: On Mon, 2023-02-27 at 06:28 +, Jan Bilek wrote: Our customer was able to sneak in an Unicode data into a column of a JSON Type and now that record fails on select. Would you be able to suggest any way out of this? E.g. finding infringing row, updating

Re: ERROR: unsupported Unicode escape sequence - in JSON-type column

Erik Wienhold writes: >> On 27/02/2023 13:13 CET Laurenz Albe wrote: >> I'd be curious to know how the customer managed to do that. >> Perhaps there is a loophole in PostgreSQL that needs to be fixed. > Another reason to prefer jsonb over json to reject such inputs right away. > The documentatio

  1   2   3   4   5   6   >