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 fres
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
++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.
>
> p
Hi Team,
Please ignore the name after "Hi" in the previous mail. :/
The potential bug is a mentioned in the mail.
On Tue, Jul 10, 2018 at 6:37 PM, Aditya Toshniwal <
aditya.toshni...@enterprisedb.com> wrote:
> Hi Dave,
>
> I am working on a feature to support INCLUDE
: included columns must not intersect with key columns
CREATE INDEX ind1
ON public.some_table USING btree
(id asc nulls last)
INCLUDE(id)
TABLESPACE pg_default;
This query passes and index is created.
Kindly let me know if I am missing anything.
--
Thanks and Regards,
Aditya
