TDE implementation in postgres which is in docker container

Hi All, How to implement TDE in postgres which is running docker containers. Thanks in advance. Regards, Vasu Madhineni

Re: is JIT available

> On Jul 24, 2020, at 9:55 PM, Pavel Stehule wrote: > > SELECT * FROM pg_config; That doesn't tell me whether or not it can actually be used.

Re: is JIT available

so 25. 7. 2020 v 14:04 odesílatel Scott Ribe napsal: > > On Jul 24, 2020, at 9:55 PM, Pavel Stehule > wrote: > > > > SELECT * FROM pg_config; > > That doesn't tell me whether or not it can actually be used. > It shows if Postgres was compiled with JIT support. When you run EXPLAIN ANALYZE SELE

Re: is JIT available

> On Jul 25, 2020, at 6:21 AM, Pavel Stehule wrote: > > It shows if Postgres was compiled with JIT support. > > When you run EXPLAIN ANALYZE SELECT ... then you can see info about JIT > overhead. If you don't see notices about JIT in EXPLAIN, then JIT was not > used. The presence of "jit = on

Re: is JIT available

so 25. 7. 2020 v 14:33 odesílatel Scott Ribe napsal: > > On Jul 25, 2020, at 6:21 AM, Pavel Stehule > wrote: > > > > It shows if Postgres was compiled with JIT support. > > > > When you run EXPLAIN ANALYZE SELECT ... then you can see info about JIT > overhead. If you don't see notices about JIT

Re: is JIT available

## Scott Ribe (scott_r...@elevated-dev.com): > So JIT is enabled in your conf, how can you tell from within a client > session whether it's actually available (PG compiled with it and > compiler available)? pg_jit_available() boolean is JIT compilation available in this session https://www.pos

Re: bad JIT decision

David Rowley writes: > On Sat, 25 Jul 2020 at 10:42, David Rowley wrote: >> I think plan cost overestimation is a common cause of unwanted jit too. >> It would be good to see the EXPLAIN ANALYZE so we knew if that was the >> case here. > So Scott did send me the full EXPLAIN ANALYZE for this pri

Re: bad JIT decision

Andres Freund writes: > On 2020-07-24 18:37:02 -0400, Tom Lane wrote: >> Yeah. I'm fairly convinced that the v12 defaults are far too low, >> because we are constantly seeing complaints of this sort. > I think the issue is more that we need to take into accoutn that the > overhead of JITing scal

Format generation_expression

Hi, Currently, I have a problem. I am working on a project with generated columns. I try to implement the generated column feature in the typeorm project. The thing is, I don't want to drop and add a generated column every time the application starts. Therefore I need a way to check whether a g

Re: bad JIT decision

David Rowley writes: > ... nested at the bottom level join, about 6 joins deep. The lack of > any row being found results in upper level joins not having to do > anything, and the majority of the plan is (never executed). On re-reading this, that last point struck me forcibly. If most of the pl

Re: TDE implementation in postgres which is in docker container

On 7/24/20 11:38 AM, Vasu Madhineni wrote: Hi All, How to implement TDE in postgres which is running docker containers. Postgres does not have TDE.  You need to encrypt at the filesystem level. -- Angular momentum makes the world go 'round.

plphyton function - return each list value as a row ?

Hi All, I am trying to create my first plphyton function ( retrieving earthquake data from an API) . Overall I was able to get one single row to be returned, but am struggling how to return the entire list I have as multiple rows - see below. Currently I get the following error when running the G

RE: plphyton function - return each list value as a row ?

Answering my own question I got it to work by a tiny change add SETOF for the return definition: Cheers Karsten ... RETURNS SETOF equake_values AS $$ ... -Original Message- From: karsten [mailto:kars...@terragis.net] Sent: Saturday, July 25, 2020 14:42 To: pgsql-general@lists.postgresql.

Re: bad JIT decision

On Sun, 26 Jul 2020 at 02:17, Tom Lane wrote: > > David Rowley writes: > > On Sat, 25 Jul 2020 at 10:42, David Rowley wrote: > >> I think plan cost overestimation is a common cause of unwanted jit too. > >> It would be good to see the EXPLAIN ANALYZE so we knew if that was the > >> case here. >

Re: bad JIT decision

On Sun, 26 Jul 2020 at 02:23, Tom Lane wrote: > > Andres Freund writes: > > On 2020-07-24 18:37:02 -0400, Tom Lane wrote: > >> Yeah. I'm fairly convinced that the v12 defaults are far too low, > >> because we are constantly seeing complaints of this sort. > > > I think the issue is more that we

Re: bad JIT decision

On Sun, 26 Jul 2020 at 02:54, Tom Lane wrote: > > David Rowley writes: > > ... nested at the bottom level join, about 6 joins deep. The lack of > > any row being found results in upper level joins not having to do > > anything, and the majority of the plan is (never executed). > > On re-reading

Re: [SOLUTION] Slow or Cannot Connect to PostgreSQL Instance Service on Windows 10

On 24-07-2020 06:16, Adrian Klaver wrote: On 7/22/20 4:49 PM, Surya Widyanto wrote: On 23-07-2020 06:12, Rob Sargent wrote: On Jul 22, 2020, at 4:58 PM, Surya Widyanto > wrote: On 23-07-2020 05:26, Adrian Klaver wrote: On 7/22/20 10:24 AM, Surya Widyanto wrote: H