Re: BUG #18308: SQL query information_schema metadata got error: server process was terminated by signal 11: Segment

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: jason(dot)chentj(at)homecredit(dot)cn, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18308: SQL query information_schema metadata got error: server process was terminated by signal 11: Segment
Date: 2024-01-24 15:32:20
Message-ID: c16abc6aa3c47e493a0024d828903fedd4a1dc5f.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, 2024-01-24 at 06:43 +0000, PG Bug reporting form wrote:
> Today when I ran the SQL query from  information_schema to get table
> relationship as below:

I cannot reproduce that.

Can you provide a complete test case that I can tun on an empty
database to reproduce the problem?

A stack trace from the crash could also be helpful.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexander Lakhin 2024-01-24 16:00:00 Re: BUG #18309: TOASTed entry in pg_subscription provokes an assertion failure
Previous Message Laurenz Albe 2024-01-24 15:28:45 Re: BUG #18295: In PostgreSQL a unique index on targeted columns is sufficient to support a foreign key