Hi,
On 08/02/2025 20:28, Cihat Küçükbağrıaçık wrote:
Hi Community,
I have a PostgreSQL 17.2 database running on Ubuntu 22.04. I'm trying to
install the |passwordcheck| extension, but I keep getting a "file not
found" error.
postgres=# create extension passwordcheck;
ERROR: extension "passw
Thanks for your quick responses.
I have just added the session related timeout parameters in the
postgresql.conf file also tried tweaking with different values/patterns
like ('1min', '1 min', 8, 10s, '10s', '10 s')
but i get an immediate error after reloading the configuration file.
*postgre
> On 12 Jan 2022, at 4:35 PM, Ian Lawrence Barwick wrote:
>
> 2022年1月12日(水) 20:16 Amine Tengilimoglu :
>>
>> Hi;
>>
>> I want to read an external pdf file from postgres. pdf file will exist
>> on the disk. postgres only know the disk full path as metadata. Is there any
>> software or e
Thanks for clarifying, got it.
Is this issue specifically reported in only the PG 15 version? more syntax
sensitivity.
On Mon, Feb 10, 2025 at 6:09 PM rob stone wrote:
>
>
> On Mon, 2025-02-10 at 16:06 +0530, Mukesh Tanuku wrote:
> > Thanks for your quick responses.
> >
> > I have just added the
Hi,
Thank you for your response. Yes, it turns out that it works without
needing to run *CREATE EXTENSION*. My issue has been resolved. Thank you
for your help.
Best regards.
>
> -- Forwarded message -
> Gönderen: Guillaume Lelarge
> Date: 10 Şub 2025 Pzt, 13:28
> Subject: Re:
=?UTF-8?B?Q2loYXQgS8O8w6fDvGtiYcSfcsSxYcOnxLFr?=
writes:
> I have also observed that the *passwordcheck.so* file exists in the
> *"/usr/lib/postgresql/17/lib/"* directory. It seems that, for some reason,
> when the PostgreSQL service starts, it is unable to read the
> *passwordcheck.so* file and
Mukesh Tanuku writes:
> Is this issue specifically reported in only the PG 15 version? more syntax
> sensitivity.
PG 15 and up report the syntax error differently.
regression=# set foo = 15min;
ERROR: trailing junk after numeric literal at or near "15min"
LINE 1: set foo = 15min;
Thanks for all of you for responding and clarifying things. Really
appreciate it.
We finally confirmed that it is a SET command issue where the AWX
application is firing the query without quotes and it's a known bug from
their end.
Thank you once again.
Regards
Mukesh Tanuku
On Mon, Feb 10, 2025
On Mon, 2025-02-10 at 16:06 +0530, Mukesh Tanuku wrote:
> Thanks for your quick responses.
>
> I have just added the session related timeout parameters in the
> postgresql.conf file also tried tweaking with different
> values/patterns like ('1min', '1 min', 8, 10s, '10s', '10 s')
>
> but i
I see there is some open PR in awx-operator (
https://github.com/ansible/awx/issues/15406) which is related to this. AWX
is connected to DB in my case.
On Mon, Feb 10, 2025 at 7:04 PM Mukesh Tanuku
wrote:
> Thanks for clarifying, got it.
> Is this issue specifically reported in only the PG 15 ve
Hello,
is there any plan for another minor release? I'm facing troubles with
some queries on PostgreSQL 17 and 16 blocking upgrades causing "wrong
varnullingrels" error. Per our conversation in CSPUG (Czech language,
https://groups.google.com/g/postgresql-cz/c/_jah9d1U1R8/m/HBJszs-2AwAJ)
we have f
=?UTF-8?B?Sm9zZWYgxaBpbcOhbmVr?= writes:
> is there any plan for another minor release?
https://www.postgresql.org/developer/roadmap/
regards, tom lane
12 matches
Mail list logo