pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedERROR
18+ messages / 14 participants
[nested] [flat]
* ERROR
@ 2003-11-22 13:47 Ashok Chauhan <ashok@kalculate.com>
0 siblings, 2 replies; 18+ messages in thread
From: Ashok Chauhan @ 2003-11-22 13:47 UTC (permalink / raw)
To: pgsql-admin
# include <stdlib.h>
# include <libpq-fe.h>
int main()
{
int feild;
PGresult *result;
PGconn *conn;
conn = PQconnectdb("database");
result = PQexec (conn, "select * from teblename");
feild = PQntuples (result);
printf("%d",feild);
PQclear(result);
PQfinish (conn);
return (1);
}
I RUN THE ABOVE PROGRAM BUT IT GIVE SOME ERRORS THAT ARE FOLLOWS:-
/tmp/ccApFcdl.o: In function `main':
/tmp/ccApFcdl.o(.text+0x19): undefined reference to `PQconnectdb'
/tmp/ccApFcdl.o(.text+0x2f): undefined reference to `PQexec'
/tmp/ccApFcdl.o(.text+0x40): undefined reference to `PQntuples'
/tmp/ccApFcdl.o(.text+0x64): undefined reference to `PQclear'
/tmp/ccApFcdl.o(.text+0x72): undefined reference to `PQfinish'
collect2: ld returned 1 exit status
HELP ME
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: ERROR
@ 2003-11-22 14:03 Bruno LEVEQUE <bruno.leveque@net6d.com>
parent: Ashok Chauhan <ashok@kalculate.com>
1 sibling, 0 replies; 18+ messages in thread
From: Bruno LEVEQUE @ 2003-11-22 14:03 UTC (permalink / raw)
To: Ashok Chauhan <ashok@kalculate.com>; +Cc: pgsql-admin
Hi,
Change your connect line with :
conn = PQconnectdb("dbname='database'");
Bruno
Ashok Chauhan wrote:
># include <stdlib.h>
># include <libpq-fe.h>
>int main()
>{
> int feild;
> PGresult *result;
> PGconn *conn;
> conn = PQconnectdb("database");
> result = PQexec (conn, "select * from teblename");
> feild = PQntuples (result);
> printf("%d",feild);
> PQclear(result);
> PQfinish (conn);
> return (1);
>
>}
>
>I RUN THE ABOVE PROGRAM BUT IT GIVE SOME ERRORS THAT ARE FOLLOWS:-
>
>/tmp/ccApFcdl.o: In function `main':
>/tmp/ccApFcdl.o(.text+0x19): undefined reference to `PQconnectdb'
>/tmp/ccApFcdl.o(.text+0x2f): undefined reference to `PQexec'
>/tmp/ccApFcdl.o(.text+0x40): undefined reference to `PQntuples'
>/tmp/ccApFcdl.o(.text+0x64): undefined reference to `PQclear'
>/tmp/ccApFcdl.o(.text+0x72): undefined reference to `PQfinish'
>collect2: ld returned 1 exit status
>
>HELP ME
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>
>
>
--
Bruno LEVEQUE
System Engineer
SARL NET6D
bruno.leveque@net6d.com
http://www.net6d.com
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: ERROR
@ 2003-11-22 16:14 Stephan Szabo <sszabo@megazone.bigpanda.com>
parent: Ashok Chauhan <ashok@kalculate.com>
1 sibling, 0 replies; 18+ messages in thread
From: Stephan Szabo @ 2003-11-22 16:14 UTC (permalink / raw)
To: Ashok Chauhan <ashok@kalculate.com>; +Cc: pgsql-admin
On Sat, 22 Nov 2003, Ashok Chauhan wrote:
>
> # include <stdlib.h>
> # include <libpq-fe.h>
> int main()
> {
> int feild;
> PGresult *result;
> PGconn *conn;
> conn = PQconnectdb("database");
> result = PQexec (conn, "select * from teblename");
> feild = PQntuples (result);
> printf("%d",feild);
> PQclear(result);
> PQfinish (conn);
> return (1);
>
> }
>
> I RUN THE ABOVE PROGRAM BUT IT GIVE SOME ERRORS THAT ARE FOLLOWS:-
Are you sure you're running the program when you get these errors as
opposed to compiling/linking? The below look like linking errors you'd
get if you forgot to specify that you want to link with libpq.
If you're using gcc, you probably want at least -lpq and possibly a
-L<directory containing libpq.a> on the commandline.
>
> /tmp/ccApFcdl.o: In function `main':
> /tmp/ccApFcdl.o(.text+0x19): undefined reference to `PQconnectdb'
> /tmp/ccApFcdl.o(.text+0x2f): undefined reference to `PQexec'
> /tmp/ccApFcdl.o(.text+0x40): undefined reference to `PQntuples'
> /tmp/ccApFcdl.o(.text+0x64): undefined reference to `PQclear'
> /tmp/ccApFcdl.o(.text+0x72): undefined reference to `PQfinish'
> collect2: ld returned 1 exit status
>
> HELP ME
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>
^ permalink raw reply [nested|flat] 18+ messages in thread
* Error
@ 2005-02-28 07:13 Maritza Landsberg <jesse@cks.co.za>
0 siblings, 0 replies; 18+ messages in thread
From: Maritza Landsberg @ 2005-02-28 07:13 UTC (permalink / raw)
To: pgsql-admin
Hi
I need help with the following error I am getting when trying to connect
with Microsoft Access to my Postgresql database.
FATAL 1: No host found in pg_hba.conf for IP address, database name,
postgres user...
I have changed the pg_hba.conf to include the IP address.
Please could someone assist me with this?
Thanks
Maritza Landsberg
Confidentiality Notice:
The above message and all attachments may contain privileged and confidential information intended only for the person or entity to which it is addressed. Any review, retransmission, dissemination, copy or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this message in error, please notify the sender immediately by e-mail, facsimile or telephone and thereafter delete the material from your computer. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the view of the entity transmitting the message. Computerkit Retail Systems (Pty) Ltd hereby distances itself from and accepts no liability in respect of the unauthorised use of its e-mail facility or the sending of e-mail communications for other than strictly business purposes
^ permalink raw reply [nested|flat] 18+ messages in thread
* Error
@ 2005-03-01 09:53 Allan Kamau <kamauallan@yahoo.com>
0 siblings, 0 replies; 18+ messages in thread
From: Allan Kamau @ 2005-03-01 09:53 UTC (permalink / raw)
To: jesse@cks.co.za; pgsql-admin
Be sure you've supplied the username, password and
database name when connecting, also check to see you
don't have a reject policy that may impede your
connection attempt.
Be sure to instruct postgresql to reload the
configuration files once you've modified the
pg_hba.conf file.
You may start by adding line similar to this at the
end of your pg_hba.conf file.
host all all
<your_client's_ip_address>/32 password
Where your_client's_ip_address will be the IP
address of the computer your attempting to connect to
PostgreSQL from, in your case it will be the computer
your running M$ Access from.
Allan.
--- Maritza Landsberg <jesse@cks.co.za> wrote:
> Hi
>
> I need help with the following error I am getting
> when trying to connect
> with Microsoft Access to my Postgresql database.
>
> FATAL 1: No host found in pg_hba.conf for IP
> address, database name,
> postgres user...
>
> I have changed the pg_hba.conf to include the IP
> address.
>
> Please could someone assist me with this?
>
> Thanks
>
> Maritza Landsberg
>
>
__________________________________
Do you Yahoo!?
Yahoo! Sports - Sign up for Fantasy Baseball.
http://baseball.fantasysports.yahoo.com/
^ permalink raw reply [nested|flat] 18+ messages in thread
* error
@ 2008-09-23 20:48 Carol Walter <walterc@indiana.edu>
0 siblings, 2 replies; 18+ messages in thread
From: Carol Walter @ 2008-09-23 20:48 UTC (permalink / raw)
To: pgsql-admin
Hi, Folks,
What would cause this error?
SQL error:
ERROR: could not access status of transaction 10274530
DETAIL: Could not open file "pg_clog/0009": No such file or directory.
Carol
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: error
@ 2008-09-23 20:50 Scott Marlowe <scott.marlowe@gmail.com>
parent: Carol Walter <walterc@indiana.edu>
1 sibling, 1 reply; 18+ messages in thread
From: Scott Marlowe @ 2008-09-23 20:50 UTC (permalink / raw)
To: Carol Walter <walterc@indiana.edu>; +Cc: pgsql-admin
On Tue, Sep 23, 2008 at 2:48 PM, Carol Walter <walterc@indiana.edu> wrote:
> Hi, Folks,
> What would cause this error?
> SQL error:
> ERROR: could not access status of transaction 10274530
> DETAIL: Could not open file "pg_clog/0009": No such file or directory.
Often it's a problem caused by a virus checker.
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: error
@ 2008-09-23 20:59 Carol Walter <walterc@indiana.edu>
parent: Scott Marlowe <scott.marlowe@gmail.com>
0 siblings, 0 replies; 18+ messages in thread
From: Carol Walter @ 2008-09-23 20:59 UTC (permalink / raw)
To: Scott Marlowe <scott.marlowe@gmail.com>; +Cc: pgsql-admin
There really is not pg_clog/0009 file.
On Sep 23, 2008, at 4:50 PM, Scott Marlowe wrote:
> On Tue, Sep 23, 2008 at 2:48 PM, Carol Walter <walterc@indiana.edu>
> wrote:
>> Hi, Folks,
>> What would cause this error?
>> SQL error:
>> ERROR: could not access status of transaction 10274530
>> DETAIL: Could not open file "pg_clog/0009": No such file or
>> directory.
>
> Often it's a problem caused by a virus checker.
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: error
@ 2008-09-24 02:42 Tom Lane <tgl@sss.pgh.pa.us>
parent: Carol Walter <walterc@indiana.edu>
1 sibling, 1 reply; 18+ messages in thread
From: Tom Lane @ 2008-09-24 02:42 UTC (permalink / raw)
To: Carol Walter <walterc@indiana.edu>; +Cc: pgsql-admin
Carol Walter <walterc@indiana.edu> writes:
> What would cause this error?
> ERROR: could not access status of transaction 10274530
> DETAIL: Could not open file "pg_clog/0009": No such file or directory.
We've seen that caused by bugs that made Postgres throw away clog files
too soon; but as far as I know those bugs were all squashed in recent
releases. What PG version is this? What files *are* present in
pg_clog, and what are their mod times? Have you had any system crashes
recently?
regards, tom lane
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: error
@ 2008-09-24 03:39 Carol Walter <walterc@indiana.edu>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 18+ messages in thread
From: Carol Walter @ 2008-09-24 03:39 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-admin
I've had no system crashes. I'm embarrassed to say that I may have
inadvertently caused this problem when I was do "house cleaning" a
couple of weeks ago.
When I upgrade, how to I get my data when pg_dumpall won't run?
Carol
On Sep 23, 2008, at 10:42 PM, Tom Lane wrote:
> Carol Walter <walterc@indiana.edu> writes:
>> What would cause this error?
>
>> ERROR: could not access status of transaction 10274530
>> DETAIL: Could not open file "pg_clog/0009": No such file or
>> directory.
>
> We've seen that caused by bugs that made Postgres throw away clog
> files
> too soon; but as far as I know those bugs were all squashed in recent
> releases. What PG version is this? What files *are* present in
> pg_clog, and what are their mod times? Have you had any system
> crashes
> recently?
>
> regards, tom lane
^ permalink raw reply [nested|flat] 18+ messages in thread
* error
@ 2010-03-19 01:23 Vitaly Burshteyn <vburshteyn@broadway.com>
0 siblings, 1 reply; 18+ messages in thread
From: Vitaly Burshteyn @ 2010-03-19 01:23 UTC (permalink / raw)
To: pgsql-admin
Ho folks,
Was wandering if anybody can point me in the right direction. I am
using walmgr to move WAL files from primary to stand by server.
And I keep getting this in my log files:
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(453)
[sender=2.6.9]
2010-03-18 21:20:22,194 10972 CRITICAL rsync exec failed, res=12
2010-03-18 21:20:22,197 10972 INFO got SystemExit(1), exiting
LOG: archive command failed with exit code 1
DETAIL: The failed archive command was:
/skytools-2.1.11/python/walmgr.py /skytools-2.1.11/python/wal-master.ini
xarchive pg_xlog/000000010000000000000000 00000001000000$
Host key verification failed.
I know there is nothing wrong with my host key as I can move between the
servers with out any issues.
Thanks,
____________________________________
The information contained in this transmission may contain privileged
and confidential information. It is intended only for the use of the
person(s) named above. If you are not the intended recipient, you are
hereby notified that any review, dissemination, distribution or
duplication of this communication is strictly prohibited. If you are
not the intended recipient, please contact the sender by reply email
and destroy all copies of the original message.
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: error
@ 2010-03-19 06:36 Devrim GÜNDÜZ <devrim@gunduz.org>
parent: Vitaly Burshteyn <vburshteyn@broadway.com>
0 siblings, 0 replies; 18+ messages in thread
From: Devrim GÜNDÜZ @ 2010-03-19 06:36 UTC (permalink / raw)
To: Vitaly Burshteyn <vburshteyn@broadway.com>; +Cc: pgsql-admin
On Thu, 2010-03-18 at 21:23 -0400, Vitaly Burshteyn wrote:
> Host key verification failed.
>
> I know there is nothing wrong with my host key as I can move between
> the servers with out any issues.
Host key != ssh key.
You can easily reproduce this issue by trying to ssh from master to
slave server as user postgres (or whatever). If you are sure that
nothing is wrong, feel free to delete the related entry in
~/ssh/known_hosts file, and ssh to the slave server manually to test.
--
Devrim GÜNDÜZ
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
PostgreSQL RPM Repository: http://yum.pgrpms.org
Community: devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org Twitter: http://twitter.com/devrimgunduz
Attachments:
[application/pgp-signature] signature.asc (197B, ../../1268980587.2262.21.camel@hp-laptop2.gunduz.org/2-signature.asc)
download
^ permalink raw reply [nested|flat] 18+ messages in thread
* Error
@ 2023-11-05 15:00 Rajesh Kumar <rajeshkumar.dba09@gmail.com>
0 siblings, 2 replies; 18+ messages in thread
From: Rajesh Kumar @ 2023-11-05 15:00 UTC (permalink / raw)
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Hi all,
I am receiving the following error in postgres log:
FATAL,57P01,"terminating connection due to administrator command"...
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Error
@ 2023-11-05 15:37 David G. Johnston <david.g.johnston@gmail.com>
parent: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
1 sibling, 1 reply; 18+ messages in thread
From: David G. Johnston @ 2023-11-05 15:37 UTC (permalink / raw)
To: Rajesh Kumar <rajeshkumar.dba09@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
On Sun, Nov 5, 2023 at 8:00 AM Rajesh Kumar <rajeshkumar.dba09@gmail.com>
wrote:
> Hi all,
>
> I am receiving the following error in postgres log:
>
> FATAL,57P01,"terminating connection due to administrator command"...
>
>
> From application side, they are getting following error:
>
> Psqlexception: FATAL,: terminating connection due to administrator command.
>
>
> How to resolve this?
>
>
Tell your administrator not to terminate connections.
David J.
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Error
@ 2023-11-05 15:46 Rajesh Kumar <rajeshkumar.dba09@gmail.com>
parent: David G. Johnston <david.g.johnston@gmail.com>
0 siblings, 1 reply; 18+ messages in thread
From: Rajesh Kumar @ 2023-11-05 15:46 UTC (permalink / raw)
To: David G. Johnston <david.g.johnston@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
I am the admin with less than a year and exp.....I am not terminating any
connections ..
Is it because of vacuuming?
On Sun, 5 Nov 2023, 21:07 David G. Johnston, <david.g.johnston@gmail.com>
wrote:
> On Sun, Nov 5, 2023 at 8:00 AM Rajesh Kumar <rajeshkumar.dba09@gmail.com>
> wrote:
>
>> Hi all,
>>
>> I am receiving the following error in postgres log:
>>
>> FATAL,57P01,"terminating connection due to administrator command"...
>>
>>
>> From application side, they are getting following error:
>>
>> Psqlexception: FATAL,: terminating connection due to administrator
>> command.
>>
>>
>> How to resolve this?
>>
>>
> Tell your administrator not to terminate connections.
>
> David J.
>
>
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Error
@ 2023-11-05 15:49 Holger Jakobs <holger@jakobs.com>
parent: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
0 siblings, 1 reply; 18+ messages in thread
From: Holger Jakobs @ 2023-11-05 15:49 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
Am 05.11.23 um 16:46 schrieb Rajesh Kumar:
> I am the admin with less than a year and exp.....I am not terminating
> any connections ..
>
> Is it because of vacuuming?
>
> On Sun, 5 Nov 2023, 21:07 David G. Johnston,
> <david.g.johnston@gmail.com> wrote:
>
> On Sun, Nov 5, 2023 at 8:00 AM Rajesh Kumar
> <rajeshkumar.dba09@gmail.com> wrote:
>
> Hi all,
>
> I am receiving the following error in postgres log:
>
> FATAL,57P01,"terminating connection due to administrator
> command"...
>
>
> From application side, they are getting following error:
>
> Psqlexception: FATAL,: terminating connection due to
> administrator command.
>
>
> How to resolve this?
>
>
> Tell your administrator not to terminate connections.
>
> David J.
>
No, some application has called pg_terminate_backend() function or the
server was shut down.
see
https://www.postgresql.org/docs/current/functions-admin.html#FUNCTIONS-ADMIN-SIGNAL
--
Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012
Attachments:
[application/pgp-signature] OpenPGP_signature (202B, ../../8e083b7c-62af-289b-9665-997a38dbd65f@jakobs.com/3-OpenPGP_signature)
download
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Error
@ 2023-11-05 16:19 Tom Lane <tgl@sss.pgh.pa.us>
parent: Holger Jakobs <holger@jakobs.com>
0 siblings, 0 replies; 18+ messages in thread
From: Tom Lane @ 2023-11-05 16:19 UTC (permalink / raw)
To: Rajesh Kumar <rajeshkumar.dba09@gmail.com>; +Cc: pgsql-admin@lists.postgresql.org, Holger Jakobs <holger@jakobs.com>
Holger Jakobs <holger@jakobs.com> writes:
> Am 05.11.23 um 16:46 schrieb Rajesh Kumar:
>> Is it because of vacuuming?
> No, some application has called pg_terminate_backend() function or the
> server was shut down.
> see
> https://www.postgresql.org/docs/current/functions-admin.html#FUNCTIONS-ADMIN-SIGNAL
Concretely, this indicates that something sent the server process
a SIGTERM signal. At least within Postgres, that can only come
from pg_terminate_backend() or the postmaster sending it because
it was sent a SIGINT signal to do a fast shutdown.
So, if you weren't doing this intentionally, you need to look
for an external source of those signals.
A common newbie mistake that could lead to this is launching the
postmaster by hand, or in a shell script, in a way that doesn't
dissociate it from your terminal session. In that case typing
control-C or ending the session would deliver one of these
signals. Make sure your postmaster start script (a) uses nohup
and (b) redirects all three of postmaster's stdin, stdout, and
stderr away from the terminal.
Could be something else too, but in the end you've got something
signaling the server that you don't want.
regards, tom lane
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Error
@ 2023-11-05 16:54 Jeff Janes <jeff.janes@gmail.com>
parent: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
1 sibling, 0 replies; 18+ messages in thread
From: Jeff Janes @ 2023-11-05 16:54 UTC (permalink / raw)
To: Rajesh Kumar <rajeshkumar.dba09@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
On Sun, Nov 5, 2023 at 10:00 AM Rajesh Kumar <rajeshkumar.dba09@gmail.com>
wrote:
> Hi all,
>
> I am receiving the following error in postgres log:
>
> FATAL,57P01,"terminating connection due to administrator command"...
>
Surely there is more stuff in the log file than that. Maybe you could
expand the scope of what you quote. And include timestamps.
> How to resolve this?
>
>
There has recently been a spate of hacking attacks where the hackers
shutdown the server after starting up their payload. I'm not sure why, as
that will surely draw attention to themselves. Maybe it is to keep out
competing gangs of hackers, or maybe their payoff is now extortion (rather
than cryptomining which was very popular in the past) and so they want to
draw attention to themselves (although evidently they would be failing at
it, as you don't seem to know about their attempt yet, just its effect on
uptime). Look for new tables containing ransom notices as their contents.
Anyway, make sure you aren't being sloppy about security. Change your
passwords, especially for PostgreSQL superuser accounts, make those new
passwords actually be good ones. Better yet, also prohibit non-local
superuser connections in the first place.
Cheers,
Jeff
^ permalink raw reply [nested|flat] 18+ messages in thread
end of thread, other threads:[~2023-11-05 16:54 UTC | newest]
Thread overview: 18+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2003-11-22 13:47 ERROR Ashok Chauhan <ashok@kalculate.com>
2003-11-22 14:03 ` Bruno LEVEQUE <bruno.leveque@net6d.com>
2003-11-22 16:14 ` Stephan Szabo <sszabo@megazone.bigpanda.com>
2005-02-28 07:13 Error Maritza Landsberg <jesse@cks.co.za>
2005-03-01 09:53 Error Allan Kamau <kamauallan@yahoo.com>
2008-09-23 20:48 error Carol Walter <walterc@indiana.edu>
2008-09-23 20:50 ` Re: error Scott Marlowe <scott.marlowe@gmail.com>
2008-09-23 20:59 ` Re: error Carol Walter <walterc@indiana.edu>
2008-09-24 02:42 ` Re: error Tom Lane <tgl@sss.pgh.pa.us>
2008-09-24 03:39 ` Re: error Carol Walter <walterc@indiana.edu>
2010-03-19 01:23 error Vitaly Burshteyn <vburshteyn@broadway.com>
2010-03-19 06:36 ` Re: error Devrim GÜNDÜZ <devrim@gunduz.org>
2023-11-05 15:00 Error Rajesh Kumar <rajeshkumar.dba09@gmail.com>
2023-11-05 15:37 ` Re: Error David G. Johnston <david.g.johnston@gmail.com>
2023-11-05 15:46 ` Re: Error Rajesh Kumar <rajeshkumar.dba09@gmail.com>
2023-11-05 15:49 ` Re: Error Holger Jakobs <holger@jakobs.com>
2023-11-05 16:19 ` Re: Error Tom Lane <tgl@sss.pgh.pa.us>
2023-11-05 16:54 ` Re: Error Jeff Janes <jeff.janes@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox