Hi All,
We are using Amazon RDS PostgreSQL.
We have some multi-tenant solutions which are separating the tenant data in
Postgresql mainly in the following manner.
1. Using different schemas
2. Using different tables for different tenants.
I was just wondering what would be the best way to scale
Ok, thanks
--
Sent from Mail.ru app for Android Wednesday, 24 November 2021, 11:28pm +03:00
from Godfrin, Philippe E philippe.godf...@nov.com :
>The notion of COPY blocks and asynchronously is very interesting
>
>From: Gavin Roy < gav...@aweber.com>
>Sent: Wednesday, November 24, 2021 1:50 PM
On Mon, Nov 29, 2021 at 12:12:11PM +0100, Paul van Rixel wrote:
> Now the postgresql.logs are polluted with log connections/disconnection,
> Agent monitoring entries and in between some entries which need some
> attention but you missed them. I know the option exists to disable
> log_(dis)connectio
>
> How did you verify that, maybe some process started IO and stuck
> there? Can we check pg_stat_activity that is there some process that
> shows in the wait event as SLRURead/SLRUWrite and not coming out of
> that state?
There are no interesting entries in pg_stat_activity, and no wait events
Garfield Lewis writes:
> I am investigating whether there are any plans to have XPath 2.0 support for
> Postgres XML natively or are there any available extension packages that
> includes this support?
I don't know of anyone actively working on that. The difficulty is
that we don't especially
Hi All,
I am investigating whether there are any plans to have XPath 2.0 support for
Postgres XML natively or are there any available extension packages that
includes this support?
--
Regards,
Garfield A. Lewis
Hi,
does anyone have good or bad experience with node-pg-migrate as a schema
management/migrateion tool?
Or maybe do you have some better recommendations?
Cheers
Dirk
Hi all,
I wondered if it is worthwile to split the general postgresql.log file into
a logfile for rdbms related log entries and a connection based logfile?
Just like the Oracle rdbms.log and the listener.log for connections.
Now the postgresql.logs are polluted with log connections/disconnecti
Hello,
As part of analysis pipelines I'm dealing with stacks/trees of views — views
selecting
from other views, often recombining it with table data — which at times undergo
heavy
development. This often requires changing/discarding/renaming/… a view or many
views
somewhere in the middle of the