> On 01 Dec 2022, at 01:19, Hannes Erven wrote:
>
> You could also use a filesystem that can do atomic snapshots - like ZFS.
>
> However, I'm wondering why none of the previous respondents mentioned it?
the reason: 'cause most people are "stuck" on public clouds that does not
provide that as
Hi, minx was freeze or stop because some transactions showed state "idle in
transaction" continuously, for it to the frequency of vacuum execution has been
increased all tables, and this caused minx in the table to be updated and the
queries improved a lot and the transactions with state "idle i
Oh ok. Not to cause confusion, but after I suggested I would request an
update to the docs, I thought maybe it would be better to ask if the VTU's
code could be modified to include MVs. So I sent a request to
pgsql-hackers (I think that's the list to use for feature requests). But
from what you'
On Mon, Dec 5, 2022 at 07:27:11AM +0100, Marco Bambini wrote:
> I am using Ubuntu 14.04.5 LTS (64b bit).
> If I don't modify anything then my test application runs fine and it load
> OpenSSL 1.0.1f 6 Jan 2014 from the default directory.
I think what Michael Paquier is saying is that you have to
Hi
po 5. 12. 2022 v 15:22 odesílatel shashidhar Reddy <
shashidharreddy...@gmail.com> napsal:
> Hello Pavel,
>
> I have re installed it after upgrade as update option was not working.
>
> I could see the error in syslogs as error 4 in plpgsql_check.so and the
> databases are restarting.
>
1. pl
Some more updates
Did this start after upgrading to 22.04? Or after a certain kernel
upgrade?
For sure it only started with Ubuntu 22.04. We did not had and still
not have any issues on servers with Ubuntu 20.04 and 18.04.
It also happens with Ubuntu 22.10 (Kernel 5.19.0-23-generic). W
Hello Pavel,
I have re installed it after upgrade as update option was not working.
I could see the error in syslogs as error 4 in plpgsql_check.so and the
databases are restarting.
On Mon, 5 Dec, 2022, 5:51 pm Pavel Stehule, wrote:
>
>
> út 29. 11. 2022 v 17:28 odesílatel Pavel Stehule
> na
út 29. 11. 2022 v 17:28 odesílatel Pavel Stehule
napsal:
>
>
> út 29. 11. 2022 v 16:37 odesílatel shashidhar Reddy <
> shashidharreddy...@gmail.com> napsal:
>
>> Plogsql check version is 2.2 and one more finding is before calling the
>> function if we drop and recreate the plpgsql_check extension
po 5. 12. 2022 v 11:24 odesílatel shashidhar Reddy <
shashidharreddy...@gmail.com> napsal:
> Is there any way to get the older version 1.1 of plpgsql_check to install
> it?
>
you can compile it from source code
https://github.com/okbob/plpgsql_check
there are complete history
Regards
Pavel
>
Also, we've *never* had storage of the original text for views.
I'm a little mystified by people claiming they use original
text for vetting functions when they clearly have no equivalent
ability for views ... or are your applications completely
view-free?
Well, I would say that's annoying too!
Karsten Hilbert wrote:
> The database encoding is UTF8. That br_FR@euro.LATIN9 had
> _not_ been added manually. It is also not actively used in my
> database(s).
br_FR@euro.LATIN9 cannot be used actively in an UTF-8 database
because it's for a different encoding than the database.
It was
Hello Jeremy,
Yes and no
For Stored Functions, the “sql_body” can either be a block with BEGIN ATOMIC
... END or a single statement RETURN expression;
For a Stored Procedure, the “sql_body” is always the block.
Using “language SQL” and an “sql_body” (as per documentation) is certainly
easie
Am Mon, Dec 05, 2022 at 03:54:28PM +0530 schrieb shashidhar Reddy:
> Is there any way to get the older version 1.1 of plpgsql_check to install
> it?
Is there any way to get you to respect the kind requests to
follow this list's posting customs as expressed by the very
people you want to help you
Is there any way to get the older version 1.1 of plpgsql_check to install
it?
On Mon, 5 Dec, 2022, 1:36 pm Pavel Stehule, wrote:
>
>
> po 5. 12. 2022 v 8:42 odesílatel shashidhar Reddy <
> shashidharreddy...@gmail.com> napsal:
>
>> Pavel,
>>
>> Below is the back trace result
>>
>> libffi6-dbg li
Hi Tom:
>> I'm having problems wherein my print() statements inside my plpython stored
>> proc are not appearing in postgresql log. I tried setting the file=sys.stderr
> Hmm. I can tell you that with "logging_collector = on", I would only expect
> the logs to capture stderr output, not s
po 5. 12. 2022 v 8:42 odesílatel shashidhar Reddy <
shashidharreddy...@gmail.com> napsal:
> Pavel,
>
> Below is the back trace result
>
> libffi6-dbg libgcc1-dbg libkrb5-dbg libstdc++6-8-dbg libxml2-dbg
> postgresql-13-dbgsym postgresql-13-pldeb
> ugger-dbgsym zlib1g-dbg
>
I am sorry, I don't any
16 matches
Mail list logo
