On Thu, Oct 3, 2019 at 2:43 PM Amit Kapila wrote:
>
> On Thu, Oct 3, 2019 at 4:03 AM Tomas Vondra
> wrote:
>>
>> On Wed, Oct 02, 2019 at 04:27:30AM +0530, Amit Kapila wrote:
>> >On Tue, Oct 1, 2019 at 7:21 PM Tomas Vondra
>> >wrote:
>> >
>> >> On Tue, Oct 01, 2019 at 06:55:52PM +0530, Amit Kapi
I ran into this while trying to trigger the previously-reported segfault.
CREATE TABLE t(i) AS SELECT * FROM generate_series(1,9);
CREATE INDEX ON t(i);
[pryzbyj@database ~]$ for i in `seq 1 9`; do PGOPTIONS='-cstatement_timeout=9'
psql postgres --host /tmp --port 5678 -c "REINDEX INDEX CONCURR
Alexander Korotkov writes:
> This patch also changes the way timestamp to timestamptz cast works.
> Previously it did timestamp2tm() then tm2timestamp(). Instead, after
> timestamp2tm() it calculates timezone offset and applies it to
> original timestamp value. I hope this is correct.
I'd wonde
On Thu, Oct 3, 2019 at 4:48 PM Robert Haas wrote:
> On Tue, Oct 1, 2019 at 1:41 PM Alexander Korotkov
> wrote:
> > So, basically standard requires us to suppress any error happening in
> > filter expression.
>
> Sounds like the standard is dumb, then. :-)
>
> > But as I wrote before suppression o
Hi,
over in pgsql-bugs [1] we got a report about CREATE TEXT SEARCH
DICTIONARY causing segfaults on 12.0. Simply running
CREATE TEXT SEARCH DICTIONARY hunspell_num (Template=ispell,
DictFile=hunspell_sample_num, AffFile=hunspell_sample_long);
does trigger a crash, 100% of the time. The cr
On Sun, Oct 13, 2019 at 1:06 PM Tom Lane wrote:
> I don't think any further proof is required that this is
> a kernel bug. Where would be a good place to file it?
linuxppc-...@lists.ozlabs.org might be the right place.
https://lists.ozlabs.org/listinfo/linuxppc-dev
Justin Pryzby writes:
> On Fri, Oct 11, 2019 at 10:48:37AM -0400, Tom Lane wrote:
>> Could you provide a self-contained test case please?
> [ test case ]
Yup, fails for me too. Will look shortly.
regards, tom lane
I wrote:
> In short, my current belief is that Linux PPC64 fails when trying
> to deliver a signal if there's right around 2KB of stack remaining,
> even though it should be able to expand the stack and press on.
I figured I should try to remove some variables from the equation
by demonstrating th
On Wed, Oct 09, 2019 at 01:15:29PM -0400, Tom Lane wrote:
> Noah Misch writes:
> > On Mon, Oct 07, 2019 at 03:06:35PM -0400, Tom Lane wrote:
> >> This still fails on Apple's compilers. ...
>
> > Thanks for testing. That error boils down to "need to use some other
> > register". The second opera
On Fri, Oct 11, 2019 at 10:48:37AM -0400, Tom Lane wrote:
> Could you provide a self-contained test case please?
SET enable_partitionwise_aggregate = 'on';
SET enable_partitionwise_join = 'on';
SET max_parallel_workers_per_gather=0;
-- maybe not important but explain(settings) suggests I should in
I've now also been able to reproduce the "infinite_recurse" segfault
on wobbegong's host (or, since I was using a gcc build, I guess I
should say vulpes' host). The first-order result is that it's the
same problem with the kernel not giving us as much stack space as
we expect: there's only 1179648
Hi,
On 07/10/2019 02:55, Amit Langote wrote:
One cannot currently add partitioned tables to a publication.
create table p (a int, b int) partition by hash (a);
create table p1 partition of p for values with (modulus 3, remainder 0);
create table p2 partition of p for values with (modulus 3, rem
On 2019-10-03 16:21, Andrew Dunstan wrote:
> My new msys2 animal fairywren
Could you please check how this animal is labeled? AFAICT, this is not
an msys2 build but a mingw build (x86_64-w64-mingw32).
> has had 3 recent failures when checking
> pg_upgrade. The failures have been while running th
On 2019-10-10 10:03, Michael Paquier wrote:
> On Thu, Oct 10, 2019 at 09:08:37AM +0200, Peter Eisentraut wrote:
>> Here is my proposed patch to adjust this.
>
> Looks fine to me reading through. I think that you are right to not
> change the descriptions in build_server_final_message(), as that's
On Sat, Oct 12, 2019 at 10:49 AM Masahiko Sawada wrote:
>
> On Fri, Oct 11, 2019 at 5:13 PM Amit Kapila wrote:
> >
> > That's right, but OTOH, if the user specifies gin_pending_list_limit
> > as an option during Create Index with a value greater than GUC
> > gin_pending_list_limit, then also we w
On Sat, Oct 12, 2019 at 11:29 AM Masahiko Sawada wrote:
>
> On Sat, Oct 12, 2019 at 12:33 PM Amit Kapila wrote:
> >
> > On Fri, Oct 11, 2019 at 4:47 PM Mahendra Singh wrote:
> > >
>
> Thank you for reviewing and creating the patch!
>
> I think the patch fixes this issue correctly. Attached the u
On Wed, Oct 9, 2019 at 3:57 PM Antonin Houska wrote:
>
> Moon, Insung wrote:
>
> > On Wed, Oct 9, 2019 at 2:42 PM Antonin Houska wrote:
> > >
> > > Moon, Insung wrote:
> > >
> > > > I also tried to generate IV using PID (32bit) + tempCounter (64bit) at
> > > > first, but in the worst-case PID a
Thanks Amit for patch.
Crash is fixed by this patch.
Thanks and Regards
Mahendra Thalor
On Sat, Oct 12, 2019, 09:03 Amit Kapila wrote:
> On Fri, Oct 11, 2019 at 4:47 PM Mahendra Singh wrote:
> >
> >
> > I did some analysis and found that we are trying to free some already
> freed memory. Or
18 matches
Mail list logo
