Paul Foerster writes:
>> On 26 Nov 2024, at 17:56, Adrian Klaver wrote:
>> When you run the query again do you get the same two statements?
> Yes. I can repeat the above 4 steps as much as I want. The result remains the
> same. I would have expected to have an empty result doing the final repea
Hi Adrian,
> On 26 Nov 2024, at 17:56, Adrian Klaver wrote:
>
> Did you commit the statements?
Yes. I have autocommit on, the psql default.
> Are you using concurrent sessions to do this?
No. I do this in one session. 1. select, 2. drop, 3. add, 4. select.
> When you run the query again do y
On 11/25/24 22:04, prashant sinha wrote:
Hi Christophe,
Thank you so much for the response. One of my client is also requesting
details of licensed version of PostgreSQL. Could you please guide me
They are all licensed, it comes down to what the license restrictions
are. The community editio
On Mon, Nov 25, 2024 at 10:12:09PM -0800, Christophe Pettus wrote:
> Hello,
>
> I think there is a fundamental misunderstanding here about how
> PostgreSQL's licensing works.
>
> You do not pay for the community version of PostgreSQL. The license
> specifically states it is available without a fee
On 11/26/24 01:59, Paul Foerster wrote:
Hi,
I have a question regarding the recent security update for PostgreSQL 15.
We have a gitlab database. It used to run on the PostgreSQL 15.8 software. I
updated from 15.8 to 15.10 and executed the corrective actions as outlined in:
https://www.postgre
Hi Tom,
> On 26 Nov 2024, at 22:25, Tom Lane wrote:
>
> I would have expected an empty result too. Can you confirm that
> p_ci_pipelines used to be a partition of something? Can you show us
> the full DDL (or psql \d+ output) for the partitioned table it
> used to be part of, and for that matt
Thank you Tom!
The issue is with OS upgrade we could able replicate it.
On Mon, 25 Nov, 2024, 9:32 pm Tom Lane, wrote:
> shashidhar Reddy writes:
> > The issue is a unique key constraint with two columns one is character
> > another is integer. At some point the unique key did not work as I se
Thank you Adrian.
We replicated the issue with OS upgrade.
On Tue, 26 Nov, 2024, 11:06 am Adrian Klaver,
wrote:
> On 11/25/24 19:07, shashidhar Reddy wrote:
> > Hi Adrian,
> >
> > Thank you for your response.
> >
> > I don't think index corrupted as I can generate the ddl script from the
>
> Wh
Hi Paul,
Thanks for your help. I have fixed that issue. Now I am getting one more
issue. Can you help to fix the below error?
[postgres@post1 bin]$ /usr/pgsql-16/bin/repmgr -f
/var/lib/pgsql/repmgr.conf cluster show
WARNING: node "standby" not found in "pg_stat_replication"
ID | Name| Role
Hi,
> [postgres@post1 bin]$ ./repmgr -f /var/lib/pgsql/repmgr.conf primary register
> ERROR: following errors were found in the configuration file:
> syntax error in file "/var/lib/pgsql/repmgr.conf" line 3, near token
> "data_directory"
> syntax error in file "/var/lib/pgsql/repmgr.conf" lin
Hi,
I have a question regarding the recent security update for PostgreSQL 15.
We have a gitlab database. It used to run on the PostgreSQL 15.8 software. I
updated from 15.8 to 15.10 and executed the corrective actions as outlined in:
https://www.postgresql.org/about/news/postgresql-171-165-159-
вт, 26 нояб. 2024 г. в 14:34, Tim McLaughlin :
> Is there a way to have Postgres serialize BIGINT as a string rather than
> number in JSON? By default it does this:
>
>
> select row_to_json(row(500::bigint));
> row_to_json
> -
> {"f1":500}
>
> But I want it to do this (note that "50
Is there a way to have Postgres serialize BIGINT as a string rather than number
in JSON? By default it does this:
select row_to_json(row(500::bigint));
row_to_json
-
{"f1":500}
But I want it to do this (note that "500" is quoted):
select row_to_json(row(500::bigint));
row_to_js
Thanks for the idea. We could do that, but that would require code changes to
our thousands of lines of SQL that generate JSON to add the explicit cast to
text. I am hoping not to have to do that.
There are numerous places where I would think this would be useful:
BIGINT or NUMERIC overflows J
14 matches
Mail list logo
