Re: PostgreSQL reference coffee mug

Matthias Apitz said on Wed, 28 Jul 2021 15:40:22 +0200 >El día martes, julio 27, 2021 a las 08:32:45p. m. +0200, Matthias >Apitz escribió: > >> Thank you, Pavel. This is ofc to much for a coffee mug. For using it >> as a Reference Card in paper form, it's a pity that it is not >> written in

Re: PostgreSQL reference coffee mug

El día miércoles, julio 28, 2021 a las 06:58:08p. m. +0200, Matthias Apitz escribió: > > I'm *not* going to get into this, because I know I'm capable of spending > > days on it. I would definitely look into using different font sizes and > > colors and make it much denser, for one thing. > >

Re: DO like block for for anonymous procedures

please ignore, i overlooked the obvious. truncate table t; TRUNCATE TABLE postgres=# do $$ declare valuelist int[] := ARRAY[1,2,3,4,5,1]; -- purposely inserting duplicate that would rollback everything declare i int; begin for i in select k from unnest(valuelist) p(k) loop insert into t

DO like block for for anonymous procedures

Hi, PostgreSQL: Documentation: 13: DO Is it possible to run a DO block for multiple transactions ? I am not sure if i'll be able explain it more verbally, but -- the entire DO block like a function block is a single tx postgres=# do $$

Re: PostgreSQL reference coffee mug

Thanks to all hints about typos and bug. Attached is a corrected version as PDF. El día miércoles, julio 28, 2021 a las 11:38:22a. m. -0400, Alvaro Herrera escribió: > > I'm *not* going to get into this, because I know I'm capable of spending > days on it. I would definitely look into using

Re: PostgreSQL reference coffee mug

On 2021-Jul-28, Adrian Klaver wrote: > On 7/28/21 8:01 AM, Georg H. wrote: > To add to above: > > \set\s allone -> alone Actually that's wrong, because \s prints history not variables. This needs to read \set alone ... I'm *not* going to get into this, because I know I'm capable of

Re: PostgreSQL reference coffee mug

On 7/28/21 8:01 AM, Georg H. wrote: Hello Matthias, Am 28.07.2021 um 15:40 schrieb Matthias Apitz: El día martes, julio 27, 2021 a las 08:32:45p. m. +0200, Matthias Apitz escribió: Thank you, Pavel. This is ofc to much for a coffee mug. For using it as a Reference Card in paper form, it's a

Re: PostgreSQL reference coffee mug

Hello Matthias, Am 28.07.2021 um 15:40 schrieb Matthias Apitz: El día martes, julio 27, 2021 a las 08:32:45p. m. +0200, Matthias Apitz escribió: Thank you, Pavel. This is ofc to much for a coffee mug. For using it as a Reference Card in paper form, it's a pity that it is not written in

Re: PostgreSQL reference coffee mug

El día martes, julio 27, 2021 a las 08:32:45p. m. +0200, Matthias Apitz escribió: > Thank you, Pavel. This is ofc to much for a coffee mug. For using it as > a Reference Card in paper form, it's a pity that it is not written in English. > > I'm working on my own for the mug and will publish the

Re: pganalyze setup

On Wednesday, July 28, 2021, Atul Kumar wrote: > > Could you provide me any link or blog to install and configure > pganalyze setup on centos 7 machine. > > Also please let me whether pganalyze is an open source or not. > . > Here is their homepage: https://pganalyze.com/

pganalyze setup

Hi, Could you provide me any link or blog to install and configure pganalyze setup on centos 7 machine. Also please let me whether pganalyze is an open source or not. Regards.

How postgres is refreshing TLS certificates

Hi all, We are working on a activity in which I need to refresh the TLS certificate without restarting the my application pod. This feature is already there in Postgres. Can anyone please suggest us how postgres is implemented the same? Regards Tarkeshwar