BUG #12909: pg_dump error

dreamsxin@qq.com writes:

pg_dump: [archiver (db)] query failed: server closed the connection
unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
pg_dump: [archiver (db)] query was: SELECT
( SELECT alias FROM pg_catalog.ts_token_type('16392'::pg_catalog.oid) AS t

WHERE t.tokid = m.maptokentype ) AS tokenname,
m.mapdict::pg_catalog.regdictionary AS dictname
FROM pg_catalog.pg_ts_config_map AS m
WHERE m.mapcfg = '69497'
ORDER BY m.mapcfg, m.maptokentype, m.mapseqno

There's not really enough information here to do more than speculate,
but it appears that you've got a broken text search configuration,
perhaps a buggy custom parser definition.
What do you get from "select oid, * from pg_ts_parser"?

regards, tom lane

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Thank you, I found the reason, because Text Search Parser extension lextypes_function using the static variables return value.
Datum
zhprs_lextype(PG_FUNCTION_ARGS)
{
static LexDescr descr[27];
PG_RETURN_POINTER(descr);
}

------------------
開源是一種精神、一种信念 。

歡迎加入開源社區：
https://github.com/

------------------ 原始邮件 ------------------
发件人: "Tom Lane"<tgl@sss.pgh.pa.us>;
发送时间: 2015年4月1日(星期三) 凌晨0:53
收件人: "Dreamsxin"<dreamsxin@qq.com>;
抄送: "pgsql-bugs"<pgsql-bugs@postgresql.org>;
主题: Re: [BUGS] BUG #12909: pg_dump error

dreamsxin@qq.com writes:

pg_dump: [archiver (db)] query failed: server closed the connection
unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
pg_dump: [archiver (db)] query was: SELECT
( SELECT alias FROM pg_catalog.ts_token_type('16392'::pg_catalog.oid) AS t

WHERE t.tokid = m.maptokentype ) AS tokenname,
m.mapdict::pg_catalog.regdictionary AS dictname
FROM pg_catalog.pg_ts_config_map AS m
WHERE m.mapcfg = '69497'
ORDER BY m.mapcfg, m.maptokentype, m.mapseqno

There's not really enough information here to do more than speculate,
but it appears that you've got a broken text search configuration,
perhaps a buggy custom parser definition.
What do you get from "select oid, * from pg_ts_parser"?

regards, tom lane