Στις 8/11/24 20:16, ο/η Christophe Pettus έγραψε:
On Nov 8, 2024, at 10:12, jayesh thakare wrote:
Can we upgrade postresql from 13 to 15.4 directly?
Can we upgrade postgresql from 13 to 16 directly?
Yes.
Ideally how many major version can we jump to from older version ?
There's no practi
On Fri, Nov 8, 2024 at 11:51 PM jayesh thakare
wrote:
> Hi all,
>
> In one of our production environment..
>
> pgsql_tmp is taking about half of the space in FS.
> And temp files are from Jan 2024.
>
> Our data fs is about to reach 98% percent..
>
> Kindly suggest us what should be done to resolv
Hi all,
In one of our production environment..
pgsql_tmp is taking about half of the space in FS.
And temp files are from Jan 2024.
Our data fs is about to reach 98% percent..
Kindly suggest us what should be done to resolve this issue?
pgsql_tmp contains temperorary files during sub query ex
Sorry, it was typo. Bind variable is bigint only.
Thanks
On Fri, 8 Nov, 2024, 7:09 pm David Mullineux, wrote:
> Just spotted a potential problem. The indexed column is a bigint. Are you,
> in your prepared statement passing a string or a big int ?
> I notice your plan is doing an implicit type
On 11/8/24 10:12, jayesh thakare wrote:
Hi all,
Can we upgrade postresql from 13 to 15.4 directly?
Can we upgrade postgresql from 13 to 16 directly?
Yes either dump/restore:
https://www.postgresql.org/docs/current/app-pgdump.html
https://www.postgresql.org/docs/current/app-pgrestore.html
Or
> On Nov 8, 2024, at 10:12, jayesh thakare wrote:
> Can we upgrade postresql from 13 to 15.4 directly?
> Can we upgrade postgresql from 13 to 16 directly?
Yes.
> Ideally how many major version can we jump to from older version ?
There's no practical limit, assuming the old version is not an
Hi all,
Can we upgrade postresql from 13 to 15.4 directly?
Can we upgrade postgresql from 13 to 16 directly?
Ideally how many major version can we jump to from older version ?
Regards,
Jayeshthakare
8828986182
Postgresql dba | Clover Infotech
>
> A quick look at PLy_spi_execute_query shows that it runs each command
> in a subtransaction. It pretty much has to, because the coding rules
> for a Python method don't permit it to just longjmp out of the Python
> interpreter, so it has to set up a subtransaction so it can catch any
> error.
=?UTF-8?Q?Micha=C5=82_Albrycht?= writes:
> This proves that the plpython function affects the transaction counter much
> more. Does anyone know why?
A quick look at PLy_spi_execute_query shows that it runs each command
in a subtransaction. It pretty much has to, because the coding rules
for a Py
Because the plpython function is executing dynamic SQL?
On Fri, Nov 8, 2024 at 2:59 AM Michał Albrycht
wrote:
> I'm trying to understand why plpython function has much bigger impact on
> transaction counter in Postgres than plpgSQL function. Below is example
> which uses 2 functions:
>
> Version
Just spotted a potential problem. The indexed column is a bigint. Are you,
in your prepared statement passing a string or a big int ?
I notice your plan is doing an implicit type conversion when you run it
manually.
Sometimes the wrong type will make it not use the index.
On Fri, 8 Nov 2024, 03:07
I'm trying to understand why plpython function has much bigger impact on
transaction counter in Postgres than plpgSQL function. Below is example
which uses 2 functions:
Version with plpgSQL (each part done in separate transactions one after
another)
- check txid_current
- SQL query which calls t
12 matches
Mail list logo
