Re: Audit Role Connections

Ah, I do appear to have that enabled (inside Heroku's config), but I can't find anything like that in the logs, so I've opened a ticket with them. Thx a lot! On Fri, May 29, 2020 at 2:25 PM Peter J. Holzer wrote: > On 2020-05-29 12:42:47 -0500, Chris Morris wrote: > > We're using Heroku's PG, >

Re: Audit Role Connections

On 2020-05-29 12:42:47 -0500, Chris Morris wrote: > We're using Heroku's PG, [...] > Other than polling pg_stat_activity (which isn't 100% accurate depending on > timing), is there a good way to audit connections? To detect which roles are > being used for connections? Do you have access to the lo

Re: pg_ctl can't start db server

On 5/29/20 8:19 AM, Tanja Savic wrote: Hi, We did the upgrade of PostgreSQL 10 to 12 on linux server. Everything was fine (can connect via pgAdmin, data is there…) except two tablespaces which are still in directory for PostgreSQL 10. So we followed these steps to move tablespaces: https://

Audit Role Connections

We're using Heroku's PG, and it comes with a default, almost super-user. I'm wanting to restrict that account for only our production app servers, and have anyone connecting for personal queries to go through an assigned role by employee (that's all setup and working). Other than polling pg_stat_a

Re: pg_ctl can't start db server

Tanja Savic writes: > The configuration file path is /etc/postgresql/12/main/ postgresql.conf and > it is configured in /var/lib/postgresql/12/main/postmaster.opts: > "/usr/lib/postgresql/12/bin/postgres "-D" "/var/lib/postgresql/12/main" "-c" > "config_file=/etc/postgresql/12/main/postgresql.c

pg_ctl can't start db server

Hi, We did the upgrade of PostgreSQL 10 to 12 on linux server. Everything was fine (can connect via pgAdmin, data is there...) except two tablespaces which are still in directory for PostgreSQL 10. So we followed these steps to move tablespaces: https://www.enterprisedb.com/blog/moving-tablespa

Re: problem with self built postgres 9.0.9

Gabriele Bulfon writes: > Amazing! Rebuilt without -O and it worked like a charm! Yeah, modern compilers tend to apply optimizations that break old versions of Postgres. -O0 usually takes care of it. regards, tom lane

Re: problem with self built postgres 9.0.9

On Fri, May 29, 2020 at 7:08 AM Gabriele Bulfon wrote: > Amazing! Rebuilt without -O and it worked like a charm! > Thanks, at the moment I need to stick to 9.0.9 on this machine to be able > to reuse the same database files. > > Just to be thorough. You can update to 9.0.23 (i.e., build against

Re: problem with self built postgres 9.0.9

Amazing! Rebuilt without -O and it worked like a charm! Thanks, at the moment I need to stick to 9.0.9 on this machine to be able to reuse the same database files.   Thanks! Gabriele     Sonicle S.r.l.  :  http://www.sonicle.com Music:  http://www.gabrielebulfon.com Quantum Mechanics :  http://www

Re: problem with self built postgres 9.0.9

On 5/29/20 6:32 AM, Gabriele Bulfon wrote: Hi, I had to build postgres 9.0.9 from sources to run it under our new XStreamOS/illumos release. First 9.0 is ~ 5 years past EOL and it ended at 9.0.23. Second this is as close as I could come to a solution: https://www.postgresql.org/message-id/179

problem with self built postgres 9.0.9

Hi, I had to build postgres 9.0.9 from sources to run it under our new XStreamOS/illumos release. It used to build and run without problems in previous releases.   On this, just by running initdb I get these errors: sonicle@xstorage1:/sonicle$ initdb -D /sonicle/pgdata The files belonging to this

lib/libecpg.so.6.11 && valgrind

Hello, We're getting to the finish line in the port of our servers to PostgreSQL 11.4. and started valgrind'ing the code, as the PostgreSQL is new in the servers. Of course we have our own homework to do, but there are also complaints of valgrind pointing to the lib/libecpg.so.6.11, for example:

Re: Slow SELECT

On 2020-05-26 12:04 PM, David Rowley wrote: Since "my_table" is small, you'd likely be much better doing a manual rewrite of the query to join a subquery containing the required details from "my_table". It looks like you want the row_id from the latest tran_date for each fld_N column. So som

Re: Linux Update Experience

## Peter J. Holzer (hjp-pg...@hjp.at): > * Update frequently. That reduces the risk of needing a package which > has since been deleted from a repo, but more importantly it makes it > easier to pinpoint the cause of a conflict. This. Plus: make sure you can re-create any machine in a fully de

PG server process can keep some info of backend

Hi, Is there any extension or option in PG to keep information of any ( memory context/some memory address) of backend process in sever/postmaster main process. Thanks Braj

Re: Linux Update Experience

On 2020-05-28 14:36:34 +, Zwettler Markus (OIZ) wrote: > I'm not talking about this specific bug or its resolution. > > I want to talk about the Linux update problem in general. > > Anyone updating Linux might get such nerving dependency troubles. In my experience (having administrated Linux