Hi All,
I was reading about parallel queries in postgresql 10.
I came across the property max_parallel_workers_per_gather. It sets the
maximum number of workers that can be started by a single Gather or Gather
Merge node.
I am not able to understand gather and gather merge node.
What is the dif
Hello,
if you are attending FOSDEM 2018 and like to help with the PostgreSQL
booth or devroom, please respond to me directly.
The devroom volunteers have a guaranteed seat in the usually packed room.
We also require that every volunteer has Google Hangouts, for quick and
undisturbing commu
Thanks - works like a charm. Hmmm. I tried that earlier and got errors. I
just retried and it worked fine this time. I guess I had some other problem
- It seems that sometimes I have to exit and reenter my psql session to use
a newly interpreted version of my stored procedure, so maybe that was par
On Wed, Jan 10, 2018 at 4:27 PM, Celia McInnis
wrote:
> Hi - Is it possible to create a table inside a plpython stored procedure?
> If so, can you give an example of how to do so?
>
>
Haven't used pl/python myself but...
https://www.postgresql.org/docs/10/static/plpython-database.html
so...
Hi - Is it possible to create a table inside a plpython stored procedure?
If so, can you give an example of how to do so?
Many thanks,
Celia McInnis
For test I created two tables with 7800 partitions each and joining them sees
performance bottleneck. It is taking 5 seconds planning time. Please see
attached plan.
Regards,
Virendra
-Original Message-
From: pinker [mailto:pin...@onet.eu]
Sent: Wednesday, January 10, 2018 12:07 PM
To:
På onsdag 10. januar 2018 kl. 22:36:42, skrev Jeff Janes mailto:jeff.ja...@gmail.com>>:
On Wed, Jan 10, 2018 at 12:23 PM, Thomas Poty mailto:thomas.p...@gmail.com>> wrote: Hello, A question seems to be, according
to me, important :
How a corruption, detected thanks to data-checksums, is fixed?
On Wed, Jan 10, 2018 at 12:23 PM, Thomas Poty wrote:
> Hello,
> A question seems to be, according to me, important :
> How a corruption, detected thanks to data-checksums, is fixed?
>
Take two full cold backups of the current mess you have, including the
executables, and lock one of them away wh
Hello,
A question seems to be, according to me, important :
How a corruption, detected thanks to data-checksums, is fixed?
Thank you,
Thomas
Le 10 janv. 2018 20:39, "Andres Freund" a écrit :
> On 2018-01-09 20:51:17 -0500, Stephen Frost wrote:
> > Greetings,
> >
> > * Andreas Joseph Krogh (andr
On 2018-01-09 20:51:17 -0500, Stephen Frost wrote:
> Greetings,
>
> * Andreas Joseph Krogh (andr...@visena.com) wrote:
> > Aha, so enabling CRC causes hint-bits to be written causing extra
> > WAL-logging,
> > which woudn't be the case without CRC enabled?
> > Thanks for pointing that out.
>
>
Glauco Torres writes:
> Today I left to generate more core-dump, follow the return,
> (gdb) bt
> #0 tbm_comparator (left=left@entry=0x1d5ca08, right=right@entry=0x3acdb70)
> at tidbitmap.c:1031
> #1 0x00801268 in med3 (a=0x1d5ca08 "\350>\337\001", b=0x3acdb70
> , c=0x583ecd8 bounds>, c
>
> Might be worth comparing sha1sum's of the postgres executable between
> this server and one that's not having the problem, just to eliminate
> the corrupted-binary theory.
>
>
>
The return is the same for the two servers,
$ sha1sum /usr/pgsql-9.6/bin/postmaster
56bcb4d644a8b00f07e9bd42f9a3f02
Glauco Torres writes:
>> The system is a CentOS 7, and PG was installed using PGDG's YUM repository.
Might be worth comparing sha1sum's of the postgres executable between
this server and one that's not having the problem, just to eliminate
the corrupted-binary theory.
reg
>
> That would result in nonsensical gdb output, most likely; but Glauco's
> trace is internally consistent enough that I doubt gdb is lying to us.
> In any case, the crash is an observable fact :-(
>
>
> The system is a CentOS 7, and PG was installed using PGDG's YUM repository.
We are pretty sur
Merlin Moncure wrote:
> simple
> SELECT version();
> ...can give a lot of hints on who/what compiled the database if you don't
> know.
Probably, this is why Glauco included the output in his opening letter.
--
Álvaro Herrerahttps://www.2ndQuadrant.com/
PostgreSQL Development, 2
Alvaro Herrera writes:
> Tom Lane wrote:
>> Hm. I'm not normally one to jump to the conclusion that something is a
>> compiler bug, but it's hard to explain this stack trace any other way.
>> The value of "n" passed to the inner invocation of pg_qsort should not
>> have been more than 29914, but
Tom Lane wrote:
> Glauco Torres writes:
> > (gdb) bt
> > #0 ckpt_buforder_comparator (pa=pa@entry=0x7f6fa9ef4b2c,
> > pb=pb@entry=0x1be06d2d06644)
> > at bufmgr.c:4137
> > #1 0x00801268 in med3 (a=0x7f6fa9ef4b2c "\177\006",
> > b=0x1be06d2d06644 ,
> > c=0x2fc9dfbb1815c , cmp=0x6a4d20
> >
On Wed, Jan 10, 2018 at 11:08 AM, Tom Lane wrote:
> Glauco Torres writes:
>> (gdb) bt
>> #0 ckpt_buforder_comparator (pa=pa@entry=0x7f6fa9ef4b2c,
>> pb=pb@entry=0x1be06d2d06644)
>> at bufmgr.c:4137
>> #1 0x00801268 in med3 (a=0x7f6fa9ef4b2c "\177\006",
>> b=0x1be06d2d06644 ,
>> c=0x2fc9
Glauco Torres writes:
> (gdb) bt
> #0 ckpt_buforder_comparator (pa=pa@entry=0x7f6fa9ef4b2c,
> pb=pb@entry=0x1be06d2d06644)
> at bufmgr.c:4137
> #1 0x00801268 in med3 (a=0x7f6fa9ef4b2c "\177\006",
> b=0x1be06d2d06644 ,
> c=0x2fc9dfbb1815c , cmp=0x6a4d20
> )
> at qsort.c:107
> #2 0x00
I've run once a test on my laptop because was curious as well. From my
results (on laptop - 16GB RAM, 4 cores) the upper limit was 12k. Above it
planning time was unbearable high - much higher than execution time. It's
been tested on 9.5
--
Sent from: http://www.postgresql-archive.org/PostgreSQL
On Wednesday, January 10, 2018, Durumdara wrote:
>
> The PG is 9.4 on Linux, the DataBase encoding is:
>ENCODING = 'UTF8'
>LC_COLLATE = 'hu_HU.UTF-8'
>LC_CTYPE = 'hu_HU.UTF-8'
>
>
The collection rules for hu_HU.UTF-8 probably pretend symbols don't exist,
this is not uncomm
> >> > how can i have the same in pg10 as i have had in pg 9.x?
> >>
> >> Move the function call to the FROM clause:
> >>
> >> select g, (g - 1) % 5 + 1 from generate_series(1, 10) g;
> >
> > thank you. That is exact what i need.
> >
> >
> >> > I need it to date type to... if possible.
> >>
> >> T
On Tue, Jan 9, 2018 at 10:14 AM, Márcio A. Sepp
wrote:
>
>> > how can i have the same in pg10 as i have had in pg 9.x?
>>
>> Move the function call to the FROM clause:
>>
>> select g, (g - 1) % 5 + 1 from generate_series(1, 10) g;
>
> thank you. That is exact what i need.
>
>
>> > I need it to dat
On Mon, Jan 8, 2018 at 11:19 PM, Adrian Klaver
wrote:
> On 01/08/2018 05:25 PM, Márcio A. Sepp wrote:
>>
>>
>> Hi,
>>
>>
>> In pg10 generation series doesn't work like in 9.5.
>> Ex. in 9.5:
>> z=# select generate_series(1, 10), generate_series(1, 5);
>> generate_series | generate_series
>>
Dear Members!
Today one of hour clients reported an error.
She made a report filtered with string range, and she got wrong documents.
I checked it.
She filtered by a document nr (varchar field -> character varying(15)).
The range was: '18/0113', and '18/0212'.
Q.Close;
Q.SQL.Text := '
Hi group,
I'm using PG 9.6.6 and I have a problem with seg fault from every few days
to up to two week,
this server is a replica, the other servers (master, and other slaves) do
not have this problem.
I could not identify the problem, so I do not know what triggers the
problem, however I have the
26 matches
Mail list logo