Since we rectified the issue in ver 11, I couldn't get more details.
Now we are getting the same [ or similar ] issue in 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
When we ran the following query, in PGAdmin
Sel
Yes, we are planning to upgrade to Ver 17 soon.Yesterday, we got the similar
error in one more client place where version 15 is running in Ubuntu Server.
We are trying to figure out whether it's a network issue or corruption issue.
On Tuesday 25 February, 2025 at 08:24:44 pm IST, Adrian
Thanks
// Following is the PB code to retrieve data
ls_pack_version = fn_get_product_version()ls_pack_build =
fn_get_product_build()
Select releasenumber, buildnumber Into :ls_db_version, :ls_db_build From
public.co_version Where modulename = 'ALL'; If SQLCA.sqlcode <> 0 Then
ls_db_v
On 2/25/25 14:51, Martin Mueller wrote:
I would like to update my current version of Postgres13 on a Mac mini to
the latest version, but I can’ t find anything in the general document
that explains the procedure in terms readily understand by retired
professors of English…
I understand that t
I would like to update my current version of Postgres13 on a Mac mini to the
latest version, but I can’ t find anything in the general document that
explains the procedure in terms readily understand by retired professors of
English…
I understand that there are three items involved:
1. The
Hi Adrian,
I did receive an empty email body.
Kindly resend if you shared any information.
Thank you!
From: Adrian Klaver
Sent: Tuesday, February 25, 2025 8:41:54 PM
To: Sakshi Behl ; pgsql-gene...@postgresql.org
Subject: Re: PgSQL - SIEM Integration
On 2/24/2
On 2/25/25 09:19, Sakshi Behl wrote:
Hi Adrian,
I did receive an empty email body.
Kindly resend if you shared any information.
The convention on this list is to do inline or bottom posting, not the
top posting you are doing. As the quoted section below shows, the reply
was not empty.
Wha
Laurenz Albe writes:
> On Tue, 2025-02-25 at 17:15 +0300, Олег Самойлов wrote:
>> How to return seto records from seof record function? I tried pg_background
>> extension:
> You need to be specific:
> SELECT * FROM pg_background_result(l_id) AS (col1 integer, col2 text, ...);
> I don't think t
Thank you for your comments.
I have installed "Azure Database for PostgreSQL flexible server"
Standard_D4ds_v5 (4 vCores, USD 50.30 per vCore)
128 GiB (USD 0.09 per GiB)
High availabilty: Not enabled
Resulting in USD 200 / month
On 2/24/25 22:51, Sakshi Behl wrote:
Hi Team,
We are in the process of integrating pgSQL with our SIEM and would
appreciate your expert guidance on this matter.
Kindly refer to the attached document outlining the events of interest
and provide your input based on the relevant postgreSQL log en
On 2/25/25 04:39, o1bigtenor wrote:
On Tue, Feb 25, 2025 at 6:03 AM sivapostg...@yahoo.com
Not really a direct answer - - - but - - - have you considered
updating Postgresql.
Version 11 was EOL (end of life) over a year ago. Version 17 according
to the charts I've found
is the current version.
On Tue, 2025-02-25 at 17:15 +0300, Олег Самойлов wrote:
> Postgresql 17.2
>
> How to return seto records from seof record function? I tried pg_background
> extension:
>
> CREATE OR REPLACE FUNCTION public.autonomous (p_script text)
> RETURNS SETOF record
> LANGUAGE plpgsql
> VOLATILE STRICT PAR
I'll be happy to drop result (the procedure created to insert logs). But this does not work too. CREATE OR REPLACE PROCEDURE public.autonomous (p_script IN text)LANGUAGE plpgsqlAS $autonomous$DECLAREl_id integer;BEGINl_id := pg_background_launch(p_script);PERFORM pg_background_result(l_id);END;$aut
On Tuesday, February 25, 2025, Олег Самойлов wrote:
> Postgresql 17.2
>
> How to return seto records from seof record function? I tried
> pg_background extension:
>
>
> *CREATE* *OR* *REPLACE* *FUNCTION* public.autonomous (p_script *text*)
>
> *RETURNS* *SETOF* record
>
> *LANGUAGE* plpgsql
>
> *
Postgresql 17.2How to return seto records from seof record function? I tried pg_background extension: CREATE OR REPLACE FUNCTION public.autonomous (p_script text)RETURNS SETOF recordLANGUAGE plpgsqlVOLATILE STRICT PARALLEL UNSAFEAS $autonomous$DECLAREl_id integer;BEGINl_id := pg_background_launch(p
On Tue, Feb 25, 2025 at 8:51 AM wrote:
> Does this sound familiar anyone? Any ideas what might prompt Postgres to
> stop?
>
Postgres needs full read and write access to its own data directory. If it
doesn't, it will eventually PANIC, as your logs show.
See if you can figure out what else happen
Hello,
We experienced something strange last weekend when all of
a sudden the Postgres service was unexpectedly stopped
(see logs below).
No maintenance or scripts were running at the time, just
our usual traffic over the network doing
SELECTS/INSERTS/UPDATES on the server.
The server is a
On Tue, Feb 25, 2025 at 7:03 AM sivapostg...@yahoo.com <
sivapostg...@yahoo.com> wrote:
> 1. Why is corruption happening? How to find out the reason?
>
It sounds more like user error than actual corruption, but without more
data we cannot determine. Show us the exact commands you ran, along wit
On Tue, Feb 25, 2025 at 6:03 AM sivapostg...@yahoo.com
wrote:
>
> Hello,
>
> Using PostgreSQL 11.11, compiled by Visual C++ build 1914, 64-bit with
> Powerbuilder
>
> Recently, in one of our customers' places, we got an error while saving a
> record from our custom-built application using Power
Hello,
Using PostgreSQL 11.11, compiled by Visual C++ build 1914, 64-bit with
Powerbuilder
Recently, in one of our customers' places, we got an error while saving a
record from our custom-built application using PowerBuilder. While saving a
record, we compare a value from a table with a h
On Tue, 25 Feb 2025 at 00:12, Ron Johnson wrote:
> On Mon, Feb 24, 2025 at 5:50 PM Yongye Serkfem wrote:
>
>> Hi Everyone!
>> I am having a series of idle connections and unable to delete them with a
>> single command. Any help in realizing this would be greatly appreciated.
>>
>
> This will kil
Hi Team,
We are in the process of integrating pgSQL with our SIEM and would appreciate
your expert guidance on this matter.
Kindly refer to the attached document outlining the events of interest and
provide your input based on the relevant postgreSQL log entries.
Looking forward to hearing from
22 matches
Mail list logo
