Hi,
On Thu, Feb 27, 2020 at 6:23 PM Dave Page wrote:
> Hi
>
> On Thu, Feb 27, 2020 at 12:41 PM Tom Lane wrote:
>
>> Aditya Toshniwal writes:
>> > On Mon, Feb 24, 2020 at 12:46 PM Andres Freund
>> wrote:
>> >> This isn't reproducible here. Are you sure that you're running on a
>> >> clean inst
Hi
On Thu, Feb 27, 2020 at 12:41 PM Tom Lane wrote:
> Aditya Toshniwal writes:
> > On Mon, Feb 24, 2020 at 12:46 PM Andres Freund
> wrote:
> >> This isn't reproducible here. Are you sure that you're running on a
> >> clean installation?
>
> > Yes I did a fresh installation using installer prov
On Mon, Feb 24, 2020 at 8:20 PM Tom Lane wrote:
> Aditya Toshniwal writes:
> > On Mon, Feb 24, 2020 at 12:46 PM Andres Freund
> wrote:
> >> This isn't reproducible here. Are you sure that you're running on a
> >> clean installation?
>
> > Yes I did a fresh installation using installer provided
Aditya Toshniwal writes:
> On Mon, Feb 24, 2020 at 12:46 PM Andres Freund wrote:
>> This isn't reproducible here. Are you sure that you're running on a
>> clean installation?
> Yes I did a fresh installation using installer provided here -
> https://www.enterprisedb.com/downloads/postgresql
The
Hi Andres,
On Mon, Feb 24, 2020 at 12:46 PM Andres Freund wrote:
>
> Hi,
>
> On 2020-02-24 12:16:08 +0530, Aditya Toshniwal wrote:
> > The PG 12.2 server is crashing on setting the jit_above_cost param. Below
> > is the output.
>
> > postgres=# SELECT count(*) FROM pg_class;
> >
> > server close
Hi,
On 2020-02-24 12:16:08 +0530, Aditya Toshniwal wrote:
> The PG 12.2 server is crashing on setting the jit_above_cost param. Below
> is the output.
> postgres=# SELECT count(*) FROM pg_class;
>
> server closed the connection unexpectedly
>
> This probably means the server terminated abnorm
++hackers.
On Mon, Feb 24, 2020 at 12:16 PM Aditya Toshniwal <
aditya.toshni...@enterprisedb.com> wrote:
> Hi Team,
>
> The PG 12.2 server is crashing on setting the jit_above_cost param. Below
> is the output.
>
> postgres=# select version();
>
>
