Created materialized view in parallel by setting
max_parallel_workers_per_gather to 4. I could see parallel sessions kicking
off and creating the mview much faster than serial execution (10mins -
parallel vs over an hour - serial).
Now I want the refresh of the mview to happen taking around same
I can recommend sqlx:
https://github.com/jmoiron/sqlx
On Tue, Aug 18, 2020 at 4:56 PM Scottix wrote:
> I have been using pgx and seems to be working well.
>
> I recommend if your just starting to use the v4 version.
>
> On Tue, Aug 18, 2020 at 5:53 AM Stephen Frost wrote:
>
>> Greetings,
>>
On Tue, Aug 18, 2020 at 1:31 PM Matthias van de Meent
wrote:
> Would this extra ordering not effectively be an extra tiebreaker in
> the ordering, applied before the TID? I do not know the full
> implications of that, but I believe that would not result in the
> limitations that you are
On Tue, 18 Aug 2020 at 22:00, Peter Geoghegan wrote:
>
> On Tue, Aug 18, 2020 at 11:52 AM Matthias van de Meent
> wrote:
> > Given that the above could work, the current btree tuple ordering is
> > not optimized for opclass-equal but datum image-distinct values:
> > ordering of opclass-equal
I have been using pgx and seems to be working well.
I recommend if your just starting to use the v4 version.
On Tue, Aug 18, 2020 at 5:53 AM Stephen Frost wrote:
> Greetings,
>
> * Olivier Gautherot (ogauthe...@gautherot.net) wrote:
> > Le mar. 18 août 2020 à 09:36, Tony Shelver a écrit
> :
>
On Tue, 18 Aug 2020 at 18:44, Peter Geoghegan wrote:
>
> On Mon, Aug 17, 2020 at 11:44 PM Matthias van de Meent
> wrote:
> > But, if the ordering of operator-class equal tuples is already
> > system-defined, could the physical ordering of index tuples in a btree
> > (with deduplication enabled
On 8/18/20 1:19 PM, Jason Myers wrote:
> On Tue, Aug 18, 2020 at 3:49 PM Adrian Klaver
mailto:adrian.kla...@aklaver.com>> wrote:
> Have you tried with:
> BEGIN;
> CREATE TABLE some_table SELECT some_data FROM other_table LIMIT 1 WITH
> NO DATA;
> COMMIT;
>
> The above gets you the
> On Tue, Aug 18, 2020 at 3:49 PM Adrian Klaver
wrote:
> > Have you tried with:
> BEGIN;
> CREATE TABLE some_table SELECT some_data FROM other_table LIMIT 1 WITH
> NO DATA;
> COMMIT;
>
> The above gets you the table structure, but no data.
>
> BEGIN;
> INSERT into some_table SELECT * FROM
On Tue, Aug 18, 2020 at 11:52 AM Matthias van de Meent
wrote:
> Given that the above could work, the current btree tuple ordering is
> not optimized for opclass-equal but datum image-distinct values:
> ordering of opclass-equal values is currently determined only by tid,
> with as an example
On 8/18/20 12:35 PM, Jason Myers wrote:
Postgres 12.4
I was directed in slack to mention here that we're being impacted by
Postgres leaving orphaned pages in /base/ after a crash while a
CREATE TABLE is being run in transaction.
The issue is the same as the reproduction steps listed here
Postgres 12.4
I was directed in slack to mention here that we're being impacted by
Postgres leaving orphaned pages in /base/ after a crash while a CREATE
TABLE is being run in transaction.
The issue is the same as the reproduction steps listed here [1], that is:
- Start a CREATE TABLE
On Tue, Aug 18, 2020 at 11:52 AM Matthias van de Meent
wrote:
> Deduplication does not need to destroy semantic differences? 'equal'
> can (in my book) mean:
> - 'opclass-equal', that is the opclass returns true for an equality check
> - 'binary equal' or 'datum-equal' (? maybe incorrect term),
On Tue, Aug 18, 2020 at 9:44 AM Peter Geoghegan wrote:
> If we wanted to fix this for numeric, we'd have to invent a new
> numeric datatype (called numeric2, say). That probably isn't as hard
> as it sounds, since it could be part of the same B-Tree operator
> family as numeric. It could also be
On Mon, Aug 17, 2020 at 11:44 PM Matthias van de Meent
wrote:
> But, if the ordering of operator-class equal tuples is already
> system-defined, could the physical ordering of index tuples in a btree
> (with deduplication enabled for "unsafe" opclasses) be updated from
> [index_columns, tid] to
On Tue, Aug 18, 2020 at 8:27 AM PASCAL CROZET <
pascal.cro...@qualis-consulting.com> wrote:
> I want to import XML file into PG database table.
> I've find functions to get the XML content of a cell after imported an XML
> file with the pg_get_file function.
> But, I want to explode the XML
Hi all,
I want to import XML file into PG database table.
I've find functions to get the XML content of a cell after imported an XML file
with the pg_get_file function.
But, I want to explode the XML content to colums. How can I do this ?
PG 10 under Ubuntu 18
_
Stephen writes:
> * Adam Sjøgren (a...@koldfront.dk) wrote:
>>
>> We have 60 processes (workers) running on different machines accessing
>> the database, that all grab jobs from a queue and update rows in a table
>> after doing some calculations (which vary in time from <1s to perhaps a
>>
Stephen Frost writes:
> * Adam Sjøgren (a...@koldfront.dk) wrote:
>> Sometimes new database logins slow down, from usually taking <0.05s to
>> taking minutes. This is for psql as a normal user using Kerberos, for
>> psql as the postgres superuser, for the web-application logging into the
>>
On Tue, Aug 18, 2020, 8:04 PM Stephen Frost wrote:
> Greetings,
>
> * Adam Sjøgren (a...@koldfront.dk) wrote:
> > We have a PostgreSQL 11.3¹ running on an Ubuntu 16.04 server, which
> > sometimes exhibits a behaviour I can't quite understand: simply logging
> > into the database starts to take
Laurenz writes:
> On Tue, 2020-08-18 at 14:53 +0200, Adam Sjøgren wrote:
>>
>> We have 60 processes (workers) running on different machines accessing
>> the database, that all grab jobs from a queue and update rows in a table
>> after doing some calculations (which vary in time from <1s to
Greetings,
* Adam Sjøgren (a...@koldfront.dk) wrote:
> We have a PostgreSQL 11.3¹ running on an Ubuntu 16.04 server, which
> sometimes exhibits a behaviour I can't quite understand: simply logging
> into the database starts to take minutes to complete.
>
> We have 60 processes (workers) running
On Tue, 2020-08-18 at 14:53 +0200, Adam Sjøgren wrote:
> We have a PostgreSQL 11.3¹ running on an Ubuntu 16.04 server, which
> sometimes exhibits a behaviour I can't quite understand: simply logging
> into the database starts to take minutes to complete.
>
> We have 60 processes (workers) running
Hi,
We have a PostgreSQL 11.3¹ running on an Ubuntu 16.04 server, which
sometimes exhibits a behaviour I can't quite understand: simply logging
into the database starts to take minutes to complete.
We have 60 processes (workers) running on different machines accessing
the database, that all
Greetings,
Please don't top-post.
* Ron (ronljohnso...@gmail.com) wrote:
> Search the log file for errors?
Sadly, this doesn't actually work if you're really doing PITR- you need
to look for the specific message saying "recovery stopping before
commit" or similar, eg:
2020-08-18 12:55:31.240
Greetings,
* Olivier Gautherot (ogauthe...@gautherot.net) wrote:
> Le mar. 18 août 2020 à 09:36, Tony Shelver a écrit :
> > -- Forwarded message -
> > From: Tony Shelver
> > Date: Tue, 18 Aug 2020 at 09:33
> > Subject: Re: "Go" (lang) standard driver
> > To: Edson Richter
> >
>
Search the log file for errors?
Query the database(s) to verify that the latest data s there?
On 8/18/20 5:10 AM, Daulat Ram wrote:
Hello Team,
I want to know the best way to ensure/verify that the Point in time
recovery has done successfully after the crash and the restore.
Thanks,
Hello Team,
I want to know the best way to ensure/verify that the Point in time recovery
has done successfully after the crash and the restore.
Thanks,
Hi all.
I found some strange behaviour of postgres, which I recognise as a bug. First
of all, let me explain situation.
I created a "test bed" (not sure how to call it right), to test high
availability clusters based on Pacemaker and PostgreSQL. The test bed consist
of 12 virtual machines (on
David Gauthier wrote:
> I can avoid the error by just throwing a namespace in there...
> atletx7-reg036:/home/dgauthie[ 214 ] --> setenv PGOPTIONS "-c
> 'os.user=$USER' "
> But once in, "show os.user" is undefined.
It's documented to work [1], but you need to remove these single
quotes.
Hi Edson,
Le mar. 18 août 2020 à 09:36, Tony Shelver a écrit :
> -- Forwarded message -
> From: Tony Shelver
> Date: Tue, 18 Aug 2020 at 09:33
> Subject: Re: "Go" (lang) standard driver
> To: Edson Richter
>
>
> A quick Google search found https://github.com/lib/pq. Has 6.1K
-- Forwarded message -
From: Tony Shelver
Date: Tue, 18 Aug 2020 at 09:33
Subject: Re: "Go" (lang) standard driver
To: Edson Richter
A quick Google search found https://github.com/lib/pq. Has 6.1K stars so
I would guess fairly well used.
On Tue, 18 Aug 2020 at 05:56, Edson
Hi,
I was reading through the new features of PG13 (beta), and noticed
that deduplication is disabled for float(4, 8) and numeric (and jsonb,
...) due to that the datums of those types could be not binary equal,
but equal according for the opclass used.
But, if the ordering of operator-class
32 matches
Mail list logo
