pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedPG12 Server on crash on creating FTS dictionary
3+ messages / 2 participants
[nested] [flat]
* PG12 Server on crash on creating FTS dictionary
@ 2020-07-14 10:22 Aditya Toshniwal <aditya.toshniwal@enterprisedb.com>
0 siblings, 1 reply; 3+ messages in thread
From: Aditya Toshniwal @ 2020-07-14 10:22 UTC (permalink / raw)
To: pgsql-admin
Hi Team,
I've encountered a server crash on creating FTS dictionary with below SQLs:
CREATE TEXT SEARCH TEMPLATE public.ftstemp (
INIT = varchar_support,
LEXIZE = dispell_lexize
);
CREATE TEXT SEARCH DICTIONARY public.mydicttemp (
TEMPLATE = public.ftstemp
);
The logs says:
2020-07-14 15:09:32.350 IST [19671] LOG: server process (PID 73228) was
terminated by signal 11: Segmentation fault: 11
2020-07-14 15:09:32.350 IST [19671] DETAIL: Failed process was running:
CREATE TEXT SEARCH DICTIONARY public.mydicttemp (
TEMPLATE = public.ftstemp
);
2020-07-14 15:09:32.350 IST [19671] LOG: terminating any other active
server processes
Version:
postgres=# select version();
PostgreSQL 12.2 on x86_64-apple-darwin, compiled by Apple LLVM version 6.0
(clang-600.0.54) (based on LLVM 3.5svn), 64-bit
(1 row)
--
Thanks and Regards,
Aditya Toshniwal
pgAdmin Hacker | Sr. Software Engineer | EDB India | Pune
"Don't Complain about Heat, Plant a TREE"
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: PG12 Server on crash on creating FTS dictionary
@ 2020-07-14 13:59 Tom Lane <tgl@sss.pgh.pa.us>
parent: Aditya Toshniwal <aditya.toshniwal@enterprisedb.com>
0 siblings, 1 reply; 3+ messages in thread
From: Tom Lane @ 2020-07-14 13:59 UTC (permalink / raw)
To: Aditya Toshniwal <aditya.toshniwal@enterprisedb.com>; +Cc: pgsql-admin
Aditya Toshniwal <aditya.toshniwal@enterprisedb.com> writes:
> I've encountered a server crash on creating FTS dictionary with below SQLs:
> CREATE TEXT SEARCH TEMPLATE public.ftstemp (
> INIT = varchar_support,
> LEXIZE = dispell_lexize
> );
This is just pilot error; varchar_support() is surely not a suitable
init function for a text search template.
(The reason this command is superuser-only is exactly that we have to
trust the user to specify a sane set of functions.)
regards, tom lane
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: PG12 Server on crash on creating FTS dictionary
@ 2020-07-14 14:10 Aditya Toshniwal <aditya.toshniwal@enterprisedb.com>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 3+ messages in thread
From: Aditya Toshniwal @ 2020-07-14 14:10 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-admin
On Tue, Jul 14, 2020 at 7:29 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Aditya Toshniwal <aditya.toshniwal@enterprisedb.com> writes:
> > I've encountered a server crash on creating FTS dictionary with below
> SQLs:
>
> > CREATE TEXT SEARCH TEMPLATE public.ftstemp (
> > INIT = varchar_support,
> > LEXIZE = dispell_lexize
> > );
>
> This is just pilot error; varchar_support() is surely not a suitable
> init function for a text search template.
I have no particular use-case for this. It was just a test case and the
server crashed. Thought of sharing. Thanks.
>
>
> (The reason this command is superuser-only is exactly that we have to
> trust the user to specify a sane set of functions.)
>
> regards, tom lane
>
--
Thanks and Regards,
Aditya Toshniwal
pgAdmin Hacker | Sr. Software Engineer | EnterpriseDB India | Pune
"Don't Complain about Heat, Plant a TREE"
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2020-07-14 14:10 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-07-14 10:22 PG12 Server on crash on creating FTS dictionary Aditya Toshniwal <aditya.toshniwal@enterprisedb.com>
2020-07-14 13:59 ` Tom Lane <tgl@sss.pgh.pa.us>
2020-07-14 14:10 ` Aditya Toshniwal <aditya.toshniwal@enterprisedb.com>
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