Re: an error message that I don't understand

On Fri, May 2, 2025 at 1:25 PM Martin Mueller < martinmuel...@northwestern.edu> wrote: > > table tid from new index tuple (32586,21) overlaps with invalid duplicate > tuple at offset 120 of block 4398 in index "aacorrections_tcpreading_idx" > Read that as "your index is corrupted". > I have no

an error message that I don't understand

I get this error message: table tid from new index tuple (32586,21) overlaps with invalid duplicate tuple at offset 120 of block 4398 in index "aacorrections_tcpreading_idx" from an update query of the update table 1 set columnx = ‘yes’ where table1.xmlid in (select xmlid from table

Re: Basebackup fails without useful error message

Hello David, I saw the backup fail. The backup logged that it terminated the walsender, and correlating the moment it failed to the metrics of my storage, shows the storage at that time was facing a huge IOWAIT. And this was a network mounted storage. The backup process continued, but because of

Re: Basebackup fails without useful error message

On Sunday, October 20, 2024, Koen De Groote wrote: > > > I'm going to be testing this. If someone could confirm that this is how > writing WAL files works, that being: that it is only considered "done" when > the archive_command is done, that would be great. > The archiving of WAL files by the pr

Re: Basebackup fails without useful error message

On 10/21/24 13:49, Koen De Groote wrote: See, I'm reading that, and my conclusion is "Ah great, it will try again, everything will be fine." Unless it never completes and you hit the timeout. There's a link between the archive_command, pg_basebackup and wal_sender_timeout, but that link isn

Re: Basebackup fails without useful error message

See, I'm reading that, and my conclusion is "Ah great, it will try again, everything will be fine." There's a link between the archive_command, pg_basebackup and wal_sender_timeout, but that link isn't clear from just reading all these documentation pages when learning about their concepts separat

Re: Basebackup fails without useful error message

On 10/20/24 14:03, Koen De Groote wrote: So I'm assuming the process of writing WAL files, if there is an archive_command set, is only considered to be finished after the archive is written, not just when the WAL file is written in pg_wal. https://www.postgresql.org/docs/current/continuous-ar

Re: Basebackup fails without useful error message

Hello Adrian, and everyone else. It has finally happened, the backup ran into an error again, and the verbose output set me on the right path. I'm getting this error message: > pg_basebackup: could not receive data from WAL stream: server closed the connection unexpectedly > This pro

Re: Basebackup fails without useful error message

Hi, You can enable verbose to get more detail about what is happening during backup pg_basebackup -h your_host -U your_user -D /mnt/base_backup/dir/ -v Also examine recent postgres logs Verify backup directory permissions On Sun, 29 Sept 2024 at 19:49, Koen De Groote wrote: > Having run a baseba

Re: Basebackup fails without useful error message

On 9/29/24 08:57, Koen De Groote wrote: > What is the complete command you are using? The full command is: pg_basebackup -h localhost -p 5432 -U basebackup_user -D /mnt/base_backup/dir -Ft -z -P So output Format as tar, gzipped, and with progress being printed. > Have you looked at the Po

Re: Basebackup fails without useful error message

> What is the complete command you are using? The full command is: pg_basebackup -h localhost -p 5432 -U basebackup_user -D /mnt/base_backup/dir -Ft -z -P So output Format as tar, gzipped, and with progress being printed. > Have you looked at the Postgres log? > Is --verbose being used? This

Re: Basebackup fails without useful error message

On 9/29/24 07:48, Koen De Groote wrote: Having run a basebackup, I'm getting this output at the very end: pg_basebackup: child process exited with error 1 pg_basebackup: removing contents of data directory "/mnt/base_backup/dir/" What is the complete command you are using? Is there a way to

Basebackup fails without useful error message

Having run a basebackup, I'm getting this output at the very end: pg_basebackup: child process exited with error 1 pg_basebackup: removing contents of data directory "/mnt/base_backup/dir/" Is there a way to get more information as to what exactly happened? I'd like to look into fixing this or d

Re: Confusing error message in 15.6

On Tue, 2024-05-21 at 23:58 +, Dmitry O Litvintsev wrote: > > > I am observing the following error which confuses me: > > > > > > # psql -U postgres template1 -c "checkpoint; select > > > pg_backup_start('${dest}.tar.Z', true)" > > > CHECKPOINT > > > pg_backup_start > > > -

Re: Confusing error message in 15.6

, 2024 6:42 PM To: Dmitry O Litvintsev Cc: pgsql-generallists.postgresql.org Subject: Re: Confusing error message in 15.6 [EXTERNAL] – This message is from an external sender On Tue, May 21, 2024, 17:29 Dmitry O Litvintsev mailto:litvi...@fnal.gov>> wrote: Hi, I am observing the following

Re: Confusing error message in 15.6

On Tuesday, May 21, 2024, David G. Johnston wrote: > > On Tue, May 21, 2024, 17:29 Dmitry O Litvintsev wrote: > >> >> This is not just amusing, it is breaking my backup script after update >> from 11 to 15 (and change from pg_{start,stop}_backup to >> pg_backup_{start_stop}) >> > > > Yep, nowaday

Re: Confusing error message in 15.6

On Tue, May 21, 2024, 17:29 Dmitry O Litvintsev wrote: > Hi, > > I am observing the following error which confuses me: > > # psql -U postgres template1 -c "checkpoint; select > pg_backup_start('${dest}.tar.Z', true)" > CHECKPOINT > pg_backup_start > - > 17BF7/3009498 > (1 row)

Confusing error message in 15.6

Hi, I am observing the following error which confuses me: # psql -U postgres template1 -c "checkpoint; select pg_backup_start('${dest}.tar.Z', true)" CHECKPOINT pg_backup_start - 17BF7/3009498 (1 row) # psql -U postgres template1 -c "select pg_backup_stop(true)" ERROR: b

No error message/code for commands after libpq pipeline abortion

error message via PQresultErrorMessage and an error code via PQresultErrorField(..., PG_DIAG_SQLSTATE) set. All other, subsequently obtained results lack an error message or an SQLSTATE. I would expect something like "ERROR: command failed due to previous failure in pipeline", but I

Re: PG_Cron - Error Message Connection failed

Le lun. 15 mai 2023 à 05:12, FOUTE K. Jaurès a écrit : > > > Le dim. 14 mai 2023 à 21:12, Adrian Klaver a > écrit : > >> On 5/14/23 13:04, FOUTE K. Jaurès wrote: >> > >> > >> > Le dim. 14 mai 2023 à 16:12, Adrian Klaver > > > a écrit : >> >> > >> > Not what

Re: PG_Cron - Error Message Connection failed

Le dim. 14 mai 2023 à 21:12, Adrian Klaver a écrit : > On 5/14/23 13:04, FOUTE K. Jaurès wrote: > > > > > > Le dim. 14 mai 2023 à 16:12, Adrian Klaver > > a écrit : > > > > > Not what was requested. > > > > In the post linked to here: > > > > > https://w

Re: PG_Cron - Error Message Connection failed

On 5/14/23 13:04, FOUTE K. Jaurès wrote: Le dim. 14 mai 2023 à 16:12, Adrian Klaver > a écrit : Not what was requested. In the post linked to here: https://www.postgresql.org/message-id/CAHQ1jffWF7Y8c1X7EK3JvbLJgw1GEcVk0uPa3%2B0CJo4h8PFHVw%40

Re: PG_Cron - Error Message Connection failed

Le dim. 14 mai 2023 à 16:12, Adrian Klaver a écrit : > On 5/14/23 00:20, FOUTE K. Jaurès wrote: > > > > > > Le sam. 13 mai 2023 à 15:59, Adrian Klaver > > a écrit : > > > > On 5/13/23 00:54, FOUTE K. Jaurès wrote: > > > > > > > > > > > > >

Re: PG_Cron - Error Message Connection failed

On 5/14/23 00:20, FOUTE K. Jaurès wrote: Le sam. 13 mai 2023 à 15:59, Adrian Klaver > a écrit : On 5/13/23 00:54, FOUTE K. Jaurès wrote: > > > >     In your original post in the image under the database column it looks >     

Re: PG_Cron - Error Message Connection failed

Le sam. 13 mai 2023 à 15:59, Adrian Klaver a écrit : > On 5/13/23 00:54, FOUTE K. Jaurès wrote: > > > > > > > > > In your original post in the image under the database column it looks > > like, to my old eyes, there is a list of database names. > > > > Is that the case? > > > > Co

Re: PG_Cron - Error Message Connection failed

On 5/13/23 00:54, FOUTE K. Jaurès wrote: In your original post in the image under the database column it looks like, to my old eyes, there is a list of database names. Is that the case? Copy and paste that content in your reply. Hello @Adrian Klaver

Re: PG_Cron - Error Message Connection failed

Le ven. 12 mai 2023 à 20:21, Adrian Klaver a écrit : > On 5/12/23 09:41, FOUTE K. Jaurès wrote: > > Understand @Adrian Klaver . > > the log show: > > 2023-05-12 17:30:19.327 WAT [46190] LOG: cron job 8 starting: SELECT 1 > > 2023-05-12 17:30:19.339 WAT [46190]

Re: PG_Cron - Error Message Connection failed

On 5/12/23 09:41, FOUTE K. Jaurès wrote: Understand @Adrian Klaver  . the log show: 2023-05-12 17:30:19.327 WAT [46190] LOG:  cron job 8 starting: SELECT 1 2023-05-12 17:30:19.339 WAT [46190] LOG:  cron job 8 connection failed Well that did not go anywhere. In

Re: PG_Cron - Error Message Connection failed

Understand @Adrian Klaver . the log show: 2023-05-12 17:30:19.327 WAT [46190] LOG: cron job 8 starting: SELECT 1 2023-05-12 17:30:19.339 WAT [46190] LOG: cron job 8 connection failed Le ven. 12 mai 2023 à 17:23, Adrian Klaver a écrit : > On 5/12/23 09:22, FOUTE K. Jaurès wrote: > > 1) Please

Re: PG_Cron - Error Message Connection failed

On 5/12/23 09:22, FOUTE K. Jaurès wrote: 1) Please do not top post. Use inline posting 2) Do not use images, copy and paste as text. hello Fabricio, the listen_addresses is set to * the result of psql command line image.png The job on pg_cron image.png What does the Postgres log show when p

Re: PG_Cron - Error Message Connection failed

hello Fabricio, the listen_addresses is set to * the result of psql command line [image: image.png] The job on pg_cron [image: image.png] Le ven. 12 mai 2023 à 17:05, Fabricio Pedroso Jorge a écrit : > Try checking the view cron.job, column "nodename", if it's set to > "localhost", change it (

Re: PG_Cron - Error Message Connection failed

Try checking the view cron.job, column "nodename", if it's set to "localhost", change it (via an UPDATE) to the address defined in "listen_address" parameter and see if this works. Em sex., 12 de mai. de 2023 às 17:00, FOUTE K. Jaurès escreveu: > Hello everyone, > > Can someone help me to under

PG_Cron - Error Message Connection failed

Hello everyone, Can someone help me to understand this issue. I installed and configured pg_cron on the server and I was able to connect without providing a password using psql command line. But when i schedule a job, like this: SELECT cron.schedule( 'TEST','30 seconds', $$SELECT 1$$); the result

Re: Row Level Security Policy Name in Error Message

> On 6 Mar 2023, at 01:18, Louis Tian wrote: > Wondering whether there is a way to get the row-level security policy name in > the error message when it's violated. > I am only getting a more generic error message like this. > ERROR: new row violates row-level secur

Row Level Security Policy Name in Error Message

Hi All, Wondering whether there is a way to get the row-level security policy name in the error message when it's violated. I am only getting a more generic error message like this. ERROR: new row violates row-level security policy for table "table_name" Thanks for your help.

Re: PG 13.6 : Data corruption error message not being sent to syslog

But the error doesn't consist of any of the above codes, so why is it being skipped? On Wed, 25 May 2022, 23:11 Tom Lane, wrote: > Abhishek Bhola writes: > > This morning I noticed this error in my PG CSV log file. > > 2022-05-25 23:59:17.776 JST,,,117110,,628cf2c5.1c976,1,,2022-05-25 > 23:59:1

Re: PG 13.6 : Data corruption error message not being sent to syslog

Abhishek Bhola writes: > This morning I noticed this error in my PG CSV log file. > 2022-05-25 23:59:17.776 JST,,,117110,,628cf2c5.1c976,1,,2022-05-25 23:59:17 > JST,9/611296,0,ERROR,XX001,"uncommitted xmin 16395356 from before xid > cutoff 144683296 needs to be frozen","while scanning block 1

PG 13.6 : Data corruption error message not being sent to syslog

ins 'CODE:42P01' or \ $msg contains 'CODE:42P02' or \ $msg contains 'CODE:08006' or \ $msg contains 'CODE:42703' \ ) then stop ``` `syslog_ident` and `syslog_facility` is as follows: ``` postgres=# show syslog_ident ; syslog_ident --

Re: Error message while trying to connect from PGAdmin 4

11.11,  PGAdmin 4.27, Windows 10 Pro 20H2 Working fine till yesterday (24.11.2021).   When we tried to connect from PGAdmin, it refused to list server list.  Thought of some corruption happened, we tried to add a server we got the following error message What could be the reason for this error?  Any

Re: Error message while trying to connect from PGAdmin 4

Hello PostgreSQL 11.11,  PGAdmin 4.27, Windows 10 Pro 20H2 Working fine till yesterday (24.11.2021).   When we tried to connect from PGAdmin, it refused to list server list.  Thought of some corruption happened, we tried to add a server we got the following error message What could be the

Re: Need help understanding error message [RESOLVED]

On 10/26/21 1:17 PM, Rich Shepard wrote: On Tue, 26 Oct 2021, Rob Sargent wrote: Aren’t lines 3 and 6 duplicates? Ah, shoot! The second was supposed to be 16 and that's how I saw it when I scanned the list. The second thing I deeply learned about computer programming: it's almost certainly

Re: Need help understanding error message [RESOLVED]

On Tue, 26 Oct 2021, Rob Sargent wrote: Aren’t lines 3 and 6 duplicates? Ah, shoot! The second was supposed to be 16 and that's how I saw it when I scanned the list. Thanks! Rich

Re: Need help understanding error message

On Tue, 26 Oct 2021, Rob Sargent wrote: Are you doing a batch of updates, Yes, ... and including/generating a duplicate in there? No. Rich

Re: Need help understanding error message

> On Oct 26, 2021, at 11:06 AM, Rich Shepard wrote: > > On Tue, 26 Oct 2021, Ron wrote: > >> Show us the actual UPDATE statement. > > Ron, > > insert into contacts > (person_nbr,contact_date,contact_type,notes,next_contact) values > (1,'2021-10-26','Email','message 3','2012-11-16'), > (4,'

Re: Need help understanding error message

> On Oct 26, 2021, at 11:05 AM, Rich Shepard wrote: > > On Tue, 26 Oct 2021, Rob Sargent wrote: > >> What do you get when you select * where person_nbr = 6 and contact_date = >> ‘2021-10-26’ and contact_type = ‘Email’ from activities; ? > > Rob, > > 'Email'; > person_nbr | contact_date | c

Re: Need help understanding error message

On Tue, 26 Oct 2021, Ron wrote: Show us the actual UPDATE statement. Ron, insert into contacts (person_nbr,contact_date,contact_type,notes,next_contact) values (1,'2021-10-26','Email','message 3','2012-11-16'), (4,'2021-10-26','Email','message 3','2012-11-16'), (6,'2021-10-26','Email','messa

Re: Need help understanding error message

On Tue, 26 Oct 2021, Rob Sargent wrote: What do you get when you select * where person_nbr = 6 and contact_date = ‘2021-10-26’ and contact_type = ‘Email’ from activities; ? Rob, person_nbr | contact_date | contact_type | notes | next_contact +--+--+--

Re: Need help understanding error message

> On Oct 26, 2021, at 10:07 AM, Rob Sargent wrote: > > > >> > What do you get when you select * where person_nbr = 6 and contact_date = > ‘2021-10-26’ and contact_type = ‘Email’ from activities; ? > > > Whoa. Not sure why I put the “from” last but I’m sure you know it goes before the

Re: Need help understanding error message

On 10/26/21 11:58 AM, Rich Shepard wrote: In a database table I have these rows: # select * from contacts where person_nbr=6;  person_nbr | contact_date | contact_type |  not es   | next_conta

Re: Need help understanding error message

> On Oct 26, 2021, at 9:58 AM, Rich Shepard wrote: > > In a database table I have these rows: > # select * from contacts where person_nbr=6; > person_nbr | contact_date | contact_type | > not > es

Need help understanding error message

In a database table I have these rows: # select * from contacts where person_nbr=6; person_nbr | contact_date | contact_type | not es | next_contact +--+---

Re: Misplaced double quotes in error message

On 2021-10-07 10:55:09 -0400, Tom Lane wrote: > Yeah. This is not as simple as it looks, because per our message > style guidelines, double quotes are used to set off inserted text, > independently of whether it is a SQL identifier or something else. > (There is a style violation in this message:

Re: Misplaced double quotes in error message

Adrian Klaver writes: > On 10/6/21 11:17 PM, Thomas Kellerer wrote: >> consider the following table, query and error message: >> ERROR: column t.somecolumn does not exist >> Hint: Perhaps you meant to reference the column "t.someColumn". >> >> For someo

Re: Misplaced double quotes in error message

itter.com/smthakur19> <https://www.facebook.com/smthakur19>* On Thu, 7 Oct 2021 at 19:09, Adrian Klaver wrote: > On 10/6/21 11:17 PM, Thomas Kellerer wrote: > > Hello, > > > > consider the following table, query and error message: > &g

Re: Misplaced double quotes in error message

On 10/6/21 11:17 PM, Thomas Kellerer wrote: Hello, consider the following table, query and error message: create table t ( "someColumn" int ); select t.someColumn from t; ERROR: column t.somecolumn does not exist Hint: Perhaps yo

Misplaced double quotes in error message

Hello, consider the following table, query and error message: create table t ( "someColumn" int ); select t.someColumn from t; ERROR: column t.somecolumn does not exist Hint: Perhaps you meant to reference the column "t.someColumn". Fo

RE: pg 13 fatal error message mentionning "standby_mode"

Thanks Guillaume. After this change the error message will even be clearer in French than in the original version in fact. Regards, Phil De : Guillaume Lelarge Envoyé : mardi 8 juin 2021 13:21 À : Phil Florent Cc : pgsql-gene...@postgresql.org Objet : Re: pg

Re: pg 13 fatal error message mentionning "standby_mode"

Le mar. 8 juin 2021 à 13:15, Guillaume Lelarge a écrit : > Hi, > > Le mar. 8 juin 2021 à 12:11, Phil Florent a > écrit : > >> Hi, >> >> I had forgotten to include a restore_command and my standby database did >> not start (expected behavior) but the

Re: pg 13 fatal error message mentionning "standby_mode"

Hi, Le mar. 8 juin 2021 à 12:11, Phil Florent a écrit : > Hi, > > I had forgotten to include a restore_command and my standby database did > not start (expected behavior) but the error message puzzled me : > > select version(); > >

pg 13 fatal error message mentionning "standby_mode"

Hi, I had forgotten to include a restore_command and my standby database did not start (expected behavior) but the error message puzzled me : select version(); version

Re: Error message

Thx, David. I need to get some sleep. ;-) On Tue, Mar 16, 2021 at 12:35 AM David G. Johnston wrote: > > On Monday, March 15, 2021, Igor Korot wrote: >> >> [quote] >> As with PQexec, the result is normally a PGresult object whose >> contents indicate server-side success or failure. A null resul

Re: Error message

On Monday, March 15, 2021, Igor Korot wrote: > > [quote] > As with PQexec, the result is normally a PGresult object whose > contents indicate server-side success or failure. A null result > indicates out-of-memory or inability to send the command at all. Use > PQerrorMessage to get more informatio

Error message

Hi, ALL, Documentation for PQprepare states: [quote] As with PQexec, the result is normally a PGresult object whose contents indicate server-side success or failure. A null result indicates out-of-memory or inability to send the command at all. Use PQerrorMessage to get more information about suc

Re: Include 3 previous tokens in syntax error message

how it's going to present the message and what's the best way to display a syntax error. pgAdmin, for example, has requirements completely different from text-based clients. Making the basic error message longer could actually be counterproductive for clients that are making an effort on th

Include 3 previous tokens in syntax error message

Hi! Postgres returns unreadable syntax error messageges like Syntax error at or near ')' If there are many ) characters in query, it is not possible to find the palce where error occurs. STATEMENT_POSITION is difficult to use since drivers perform parameter replacements which makes this dif

Re: How to get error message details from libpq based psqlODBC driver (regression)

imary = PQresultErrorField(pgres, PG_DIAG_MESSAGE_PRIMARY); which probably gets only primary error message. To get error message detail, PG_DIAG_MESSAGE_DETAIL should used according to https://www.postgresql.org/docs/current/libpq-exec.html. Unfortunately PG_DIAG_MESSAGE_DETAIL is not used in pgsql

Re: How to get error message details from libpq based psqlODBC driver (regression)

On 2/23/20 1:06 AM, Andrus wrote: Hi! What does the log_error_verbosity setting in postgresql.conf show? It is not set. postgresql.conf contains it default value from installation: #log_error_verbosity = default    # terse, default, or verbose messages I changed it to log_error_verbosi

Re: How to get error message details from libpq based psqlODBC driver (regression)

Hi! What does the log_error_verbosity setting in postgresql.conf show? It is not set. postgresql.conf contains it default value from installation: #log_error_verbosity = default# terse, default, or verbose messages I changed it to log_error_verbosity = verbose but problem persists.

Re: How to get error message details from libpq based psqlODBC driver (regression)

s not show error message details. For example, users got only generic error message like     Connectivity error: ERROR: insert or update on table "mytable" violates     foreign key constraint  "mytable_myfield_fkey Error message details like     Key (myfield)=(mykeyvalue) is

Re: How to get error message details from libpq based psqlODBC driver (regression)

On 2/22/20 2:37 PM, Andrus wrote: Hi! I'm looking for a way to fix psqlODBC driver regression. Starting at psqlODBC 09.05.0100 when psqlODBC driver uses libpq for all operations (earlier versions used libpg only for authentication) ODBC client does not show error message details.

How to get error message details from libpq based psqlODBC driver (regression)

Hi! I'm looking for a way to fix psqlODBC driver regression. Starting at psqlODBC 09.05.0100 when psqlODBC driver uses libpq for all operations (earlier versions used libpg only for authentication) ODBC client does not show error message details. For example, users got only generic

RE: Error message restarting a database

From: Adrian Klaver Sent: Sunday, January 27, 2019 8:18:08 PM To: Begin Daniel Cc: pgsql-general Subject: Re: Error message restarting a database On 1/27/19 2:45 PM, Begin Daniel wrote: >> If you go to PGDATA.pg_tblspc do you have links to the tablespaces? >> >> I only inst

Re: Error message restarting a database

Thank, I'll have a look Sent from Galaxy S7 From: Adrian Klaver Sent: Sunday, January 27, 2019 8:18:08 PM To: Begin Daniel Cc: pgsql-general Subject: Re: Error message restarting a database On 1/27/19 2:45 PM, Begin Daniel wrote: >> I

Re: Error message restarting a database

On 1/27/19 2:45 PM, Begin Daniel wrote: If you go to PGDATA.pg_tblspc do you have links to the tablespaces? I only installed one instance of Postgres on my PC, which I use to manage two databases (postgres and osmdump). osmdump is the database that complains. Regarding the links to the table

RE: Error message restarting a database

-Original Message- From: Adrian Klaver [mailto:adrian.kla...@aklaver.com] Sent: Sunday, January 27, 2019 17:38 To: Begin Daniel Cc: pgsql-general Subject: Re: Error message restarting a database On 1/27/19 2:22 PM, Begin Daniel wrote: > -Original Message- > From: Adrian

Re: Error message restarting a database

On 1/27/19 2:22 PM, Begin Daniel wrote: -Original Message- From: Adrian Klaver [mailto:adrian.kla...@aklaver.com] Sent: Sunday, January 27, 2019 16:52 To: Begin Daniel Cc: pgsql-general Subject: Re: Error message restarting a database On 1/27/19 1:38 PM, Begin Daniel wrote

RE: Error message restarting a database

-Original Message- From: Adrian Klaver [mailto:adrian.kla...@aklaver.com] Sent: Sunday, January 27, 2019 16:52 To: Begin Daniel Cc: pgsql-general Subject: Re: Error message restarting a database On 1/27/19 1:38 PM, Begin Daniel wrote: > -Original Message- > From: Adrian

RE: Error message restarting a database

-Original Message- From: Adrian Klaver [mailto:adrian.kla...@aklaver.com] Sent: Sunday, January 27, 2019 16:52 To: Begin Daniel Cc: pgsql-general Subject: Re: Error message restarting a database On 1/27/19 1:38 PM, Begin Daniel wrote: > -Original Message- > From: Adrian

Re: Error message restarting a database

On 1/27/19 1:38 PM, Begin Daniel wrote: -Original Message- From: Adrian Klaver [mailto:adrian.kla...@aklaver.com] Sent: Sunday, January 27, 2019 16:15 To: Begin Daniel Cc: pgsql-general Subject: Re: Error message restarting a database On 1/27/19 12:56 PM, Begin Daniel wrote: Not a good

RE: Error message restarting a database

-Original Message- From: Adrian Klaver [mailto:adrian.kla...@aklaver.com] Sent: Sunday, January 27, 2019 16:15 To: Begin Daniel Cc: pgsql-general Subject: Re: Error message restarting a database On 1/27/19 12:56 PM, Begin Daniel wrote: Not a good day, forgot to actually Cc list last

Re: Error message restarting a database

On 1/27/19 12:56 PM, Begin Daniel wrote: Not a good day, forgot to actually Cc list last time. -Original Message- From: Adrian Klaver [mailto:adrian.kla...@aklaver.com] Sent: Sunday, January 27, 2019 15:43 To: Begin Daniel Subject: Re: Error message restarting a database On 1/27/19 12

Re: Error message restarting a database

On 1/27/19 12:23 PM, Begin Daniel wrote: I worked with a PostgreSQL database (9.3) for a couple of years on my PC. I shut down the PostgreSQL server about a year ago and I obviously did not access the database since. Now I am trying to access again to the database but I get the following error

Error message restarting a database

I worked with a PostgreSQL database (9.3) for a couple of years on my PC. I shut down the PostgreSQL server about a year ago and I obviously did not access the database since. Now I am trying to access again to the database but I get the following error message... FATAL: *"pg_tblspc/1136

Re: where I can find the error message for pgagent jobs

¤???·, > ^" > 7 149 1 "s" 0 "2018-06-11 12:42:05.508192+08" "00:00:00.69604" > > I actually restarted the service and it works. > Yeah - that's probably. You may have changed the pgpass.conf file, which was not loaded again without restart. -- Thanks,

Re: where I can find the error message for pgagent jobs

¤???·" does not exist LINE 4: ?¤???·, ^" 7 149 1 "s" 0 "2018-06-11 12:42:05.508192+08" "00:00:00.69604" I actually restarted the service and it works. But the chinese character is the pain in ass...

Re: where I can find the error message for pgagent jobs

t of the table: 'pgagent.pga_jobsteplog'. -- Thanks, Ashesh > > -- Original -- > *From: * "Ashesh Vashi";; > *Send time:* Monday, Jun 11, 2018 12:39 PM > *To:* "a"<372660...@qq.com>; > *Cc:* "pgsql-general"; > *Subjec

Re: where I can find the error message for pgagent jobs

"i" as last result, which is a internal failure if I'm not wrong. do you have any idea of how to get it work? -- Original -- From: "Ashesh Vashi";; Send time: Monday, Jun 11, 2018 12:39 PM To: "a"<372660...@qq.com>; Cc:

Re: where I can find the error message for pgagent jobs

Please use "pgadmin-supp...@postgresql.org" for any pgAdmin/pgAgent related questions, bugs. On Mon, Jun 11, 2018 at 9:33 AM, a <372660...@qq.com> wrote: > Hi all > > I set up a pgagent job, but it says the job was failed. > > But where I can have a look on error report message?? > > I'm using pg

where I can find the error message for pgagent jobs

Hi all I set up a pgagent job, but it says the job was failed. But where I can have a look on error report message?? I'm using pgadmin 4.3, pgagent 3.4, postgresql 10, the platform is windows server 2008 Thank you so much.

Re: Any hope for more specific error message for "value too long..."?

Ken Tanzer writes: >>> I dug in the archives and came across a crude POC hack here: >>> https://www.postgresql.org/message-id/21693.1478376...@sss.pgh.pa.us >> For that matter, it's not totally >> clear what would constitute an improvement --- what do you wish it would >> show you, exactly? > It

Re: Any hope for more specific error message for "value too long..."?

> > I dug in the archives and came across a crude POC hack here: > > https://www.postgresql.org/message-id/21693.1478376...@sss.pgh.pa.us > > At the time I didn't want to pursue it further because of Andres' > pending work on redoing expression execution, but that's landed now. > >

Re: Any hope for more specific error message for "value too long..."?

Dang. +1 for that. Not that you hadn’t thought of it, and not that it’s actually a viable solution in a jiffy, but switch that mess to JSONB and your problems are over.

Re: Any hope for more specific error message for "value too long..."?

"David G. Johnston" writes: > I seem to recall a discussion a few years back but cannot find it searching > online. The one post I did find was from 6 years ago and I was the only > respondent and basically said the same or less than I am here. I dug in the archives and came across a crude POC h

Re: Any hope for more specific error message for "value too long..."?

On Fri, Feb 16, 2018 at 5:30 PM, Ken Tanzer wrote: > > That doesn't matter much in a simple example like that, but the example > below is currently making me wish PG was just a little bit more specific. > Is there much chance of this changing in future releases? > > ​ I'm not holding my breath...

Re: Any hope for more specific error message for "value too long..."?

Ken Tanzer writes: > Hi. If you try to assign a too-long string to a field, Postgresql will say > so, but won't tell you which value/field is causing the problem: > CREATE TEMP TABLE foo (a VARCHAR(2)); > INSERT INTO foo VALUES ('ABC'); > CREATE TABLE > ERROR: value too long for type character v

Any hope for more specific error message for "value too long..."?

Hi. If you try to assign a too-long string to a field, Postgresql will say so, but won't tell you which value/field is causing the problem: CREATE TEMP TABLE foo (a VARCHAR(2)); INSERT INTO foo VALUES ('ABC'); CREATE TABLE ERROR: value too long for type character varying(2) That doesn't matter