| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | okano(dot)naoki(at)jp(dot)fujitsu(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17514: Application with embedded SQL crashes when executing EXEC SQL PREPARE |
| Date: | 2022-06-09 17:01:36 |
| Message-ID: | 2060083.1654794096@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> Application with embedded SQL crashes with segmentation fault if I execute
> EXEC SQL PREPARE
> command before executing EXEC SQL CONNECT command (*1).
> I know that it is the correct operation to execute EXEC SQL CONNECT command
> first
> and then execute EXEC SQL PREPARE command.
> But I expect this wrong operation to result in an error, not a crash.
We could do something like the attached, perhaps. Having said that,
an application that includes no error checks is pretty unlikely to
fail gracefully :-(.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| ensure-TSD-key-is-valid-before-use.patch | text/x-diff | 838 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2022-06-09 20:42:22 | BUG #17515: Change in behaviour of a composite type within a domain |
| Previous Message | Peter Eisentraut | 2022-06-09 07:38:38 | Re: psql 15beta1 does not print notices on the console until transaction completes |