pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: Andres Freund <andres@anarazel.de>
Cc: Erikjan Rijkers <er@xs4all.nl>
Cc: Himanshu Upadhyaya <upadhyaya.himanshu@gmail.com>
Cc: Julien Rouhaud <rjuju123@gmail.com>
Cc: Nikita Glukhov <n.gluhov@postgrespro.ru>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Dmitry Dolgov <9erthalion6@gmail.com>
Cc: Oleg Bartunov <obartunov@gmail.com>
Subject: Re: SQL/JSON: JSON_TABLE
Date: Wed, 06 Apr 2022 12:04:35 -0400
Message-ID: <3089003.1649261075@sss.pgh.pa.us> (raw)
In-Reply-To: <4a265059-dd92-819c-0165-43bf29f061ac@dunslane.net>
References: <CAPF61jDjaUx58qzjZT_C4X5_UP7sADtH+mfXuWimtmrjR+0HAA@mail.gmail.com>
	<5b237456-20f0-632a-c8d1-ce8ad9f47999@dunslane.net>
	<d5f0fc28-b3fd-a512-8e06-836fe9fb2117@xs4all.nl>
	<7675f582-3550-a0c6-7e6d-2febfe47bc0a@dunslane.net>
	<bbf93f05-3cc8-1efa-c08e-ec441812db52@dunslane.net>
	<c9a128c6-5ea6-0494-f281-39026fbe09eb@dunslane.net>
	<cb6ce329-2899-9a2c-80d9-62284f2e570f@dunslane.net>
	<20220406022118.3ocqvhxr6kciw5am@alap3.anarazel.de>
	<815e5590-bc8b-7d9c-3bca-e0fe15023f26@dunslane.net>
	<74116dcb-1580-b6b1-4fb6-defa2767c09d@dunslane.net>
	<20220406151142.GW10577@tamriel.snowman.net>
	<7d308e07-a633-2e78-77fb-bc26aaf8fb79@dunslane.net>
	<4a265059-dd92-819c-0165-43bf29f061ac@dunslane.net>

Andrew Dunstan <andrew@dunslane.net> writes:
>> I think we should, but I think here the obvious solution is to drop the
>> table when we're done with it. I'll test that.

> It does work, but Tom prefers not to have the test at all, so I'll just
> rip it out.

Perhaps moving it to some other place (test/modules/something?) would
be appropriate.  But I don't think that the core regression tests,
which are currently run four or more times per buildfarm cycle,
are an appropriate place for million-row test cases.

			regards, tom lane

view thread (98+ messages)  latest in thread

Message-ID: <3089003.1649261075@sss.pgh.pa.us>
Permalink:  ../3089003.1649261075@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/3089003.1649261075@sss.pgh.pa.us

copy link · copy postgr.es

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, andrew@dunslane.net, sfrost@snowman.net, andres@anarazel.de, er@xs4all.nl, upadhyaya.himanshu@gmail.com, rjuju123@gmail.com, n.gluhov@postgrespro.ru, pavel.stehule@gmail.com, 9erthalion6@gmail.com, obartunov@gmail.com
  Subject: Re: SQL/JSON: JSON_TABLE
  In-Reply-To: <3089003.1649261075@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox