Re: BUG #12909: pg_dump error - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #12909: pg_dump error
Date
Msg-id 20522.1427820827@sss.pgh.pa.us
Whole thread Raw
In response to BUG #12909: pg_dump error  (dreamsxin@qq.com)
Responses =?gb18030?B?u9i4tKO6IFtCVUdTXSBCVUcgIzEyOTA5OiBwZ19k?= =?gb18030?B?dW1wIGVycm9y?=
List pgsql-bugs
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

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: BUG #12905: Same query produces different results in SQL
Next
From: Tom Lane
Date:
Subject: Re: BUG #12908: tstzrange constructor fails when used in WHERE clause