Hi and hope this finds you well,
PostgreSQL has state of the art JSON(B) data type and query support, and
basic updates as well, eg jsonb_set().
How about enabling users to do more advanced processing of JSON
data inside the database itself, using JavaScript?
There's the PLV8 extension https://g
Is it even possible to use PG partitioning across a Foreign Server?
Hi,
On 2020-03-24 15:12:38 +0900, Michael Paquier wrote:
> > Well, there's no logging of autovacuum launchers that don't do anything
> > due to the "skipping redundant" logic, with normal log level. If somehow
> > the horizon logic of autovacuum workers gets out of whack with what
> > vacuumlazy.c
On 3/24/20 11:53 AM, Kevin Brannen wrote:
From: Rob Sargent
Sorry if I missed it, but have we seen the size range of these json files?
Not that I've seen, but that's an implementation detail for whoever is doing the work. As someone
else pointed out, pick the value as needed, whether that
From: Rob Sargent
> Sorry if I missed it, but have we seen the size range of these json files?
Not that I've seen, but that's an implementation detail for whoever is doing
the work. As someone else pointed out, pick the value as needed, whether that's
10, 100, 1000, or whatever. But issuing 10
On 3/24/20 11:29 AM, Kevin Brannen wrote:
From: pinker
it's a cloud and no plpythonu extension avaiable unfortunately
You're misunderstanding him. See David's post for an example, but the point was
that you can control all of this from an *external* Perl, Python, Bash,
whatever program
From: pinker
> it's a cloud and no plpythonu extension avaiable unfortunately
You're misunderstanding him. See David's post for an example, but the point was
that you can control all of this from an *external* Perl, Python, Bash,
whatever program on the command line at the shell.
In pseudo-c
Remund Alain writes:
> Hi all
>
>
>
> We have PostgreSql 9.6 running and started to work with materialized
> views. To refresh the materialized views, we set up a cron job that
> refreshes the materialized views on a fix schedule.
>
> Since our materialized views cache quite some data, we notic
Le mar. 24 mars 2020 à 17:00, Remund Alain a
écrit :
> Hi all
>
>
>
> We have PostgreSql 9.6 running and started to work with materialized
> views. To refresh the materialized views, we set up a cron job that
> refreshes the materialized views on a fix schedule.
>
> Since our materialized views c
Hi all
We have PostgreSql 9.6 running and started to work with materialized views. To
refresh the materialized views, we set up a cron job that refreshes the
materialized views on a fix schedule.
Since our materialized views cache quite some data, we noticed a considerable
increase in WAL files
On 2020-03-23 17:18:45 -0700, pinker wrote:
> Christopher Browne-3 wrote
> > Well, you're paying for a lot of overhead in that, as you're
> > establishing a psql command, connecting to a database, spawning a
> > backend process, starting a transactions, committing a transaction,
> > closing the bac
11 matches
Mail list logo
