Hi,
I have used this setup to do something similar.
https://github.com/2ndQuadrant/audit-trigger
KR, Mikael Gustavsson
Från: Ayub M
Skickat: den 15 december 2020 18:13:39
Till: PostgreSQL General
Ämne: postgres auditing truncates and deletes on tables
for
Hi,
We are starting our journey to migrate from Postgresql 11 to Postgresql 13 and
have run into a problem.
The postgresql 13 version of psql don´t seem to work with ssl.
We use the community built rpms on redhat 8.3:
$ rpm -q postgresql11
postgresql11-11.10-1PGDG.rhel8.x86_64
$ rpm -q postgres
On Wed, 2020-12-16 at 14:44 -0500, Jack Orenstein wrote:
> What are the pros and cons of partitioning the table?
Pro:
- it bebomes easier to get rid of old data
- autovacuum is more fun with several smaller tables
- a few select queries might become faster
Con:
- administrative overhead (crea
>
>
> I have a table in an analytics database (Postgres 12.3), that gathers data
> continuously. It is at 5B rows, with an average row size of 250 bytes. The
> table has five indexes, on bigint and varchar columns, all with keys of one
> or two columns.
>
> There are currently frequent update
Hi,
Did you also upgrade the libpq devel package?
To start, what distribution are you using, and how did you upgrade?
Are you using RHEL or Debian based packages? Did you upgrade libpq
using packages (yum/dnf update libpq or apt upgrade libpq)?
In any case, this seems like a problem with develop
I have a table in an analytics database (Postgres 12.3), that gathers data
continuously. It is at 5B rows, with an average row size of 250 bytes. The
table has five indexes, on bigint and varchar columns, all with keys of one
or two columns.
There are currently frequent updates and deletions, but
On Wed, Dec 16, 2020 at 6:55 AM M Tarkeshwar Rao <
m.tarkeshwar@ericsson.com> wrote:
> ...
>
>
> All the threshold level requirements for autovacuum was meet and there are
> about Million’s of dead tuples but autovacuum was unable to clear them,
> which cause performance issue on production
Absolutely check the logs, or do a manual vacuum verbose with setting cost
delay and cost limit (and maintenance work mem) the same as the values for
auto vacuum runs. It should work out the same and you could time it for a
period when the system is more lightly used it applicable.
If you have man
Hi,
> We have facing some discrepancy in Postgresql database related to the
> autovacuum functionality.
>
> By default autovacuum was enable on Postgres which is used to remove the dead
> tuples from the database.
>
> We have observed autovaccum cleaning dead rows from table_A but same was not
A good place to start would be here "
https://www.postgresql.org/docs/13/user-manag.html"; and "
https://www.postgresql.org/docs/13/client-authentication.html"; and "
https://www.postgresql.org/docs/current/ssl-tcp.html";
Additionally.
1) You may need to look into securing access to the physical s
Hi all,
We have facing some discrepancy in Postgresql database related to the
autovacuum functionality.
By default autovacuum was enable on Postgres which is used to remove the dead
tuples from the database.
We have observed autovaccum cleaning dead rows from table_A but same was not
functioni
Hi,
How can I protect my data by using any security on my postgres database.
Please help me.
Regards,
Atul
12 matches
Mail list logo
