| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Pete Storer <Pete(dot)Storer(at)sas(dot)com> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Query execution failure |
| Date: | 2023-01-25 20:20:10 |
| Message-ID: | D6310730-144C-4CDA-8A65-44CB2CE80510@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On Jan 25, 2023, at 11:58, Pete Storer <Pete(dot)Storer(at)sas(dot)com> wrote:
>
> I am encountering a strange error when trying to execute a complex SELECT query in Postgres. All of the details of this error are documented in the attachment.
Without opining on the bug itself, you will likely get a much better response if you put the details in plain text, rather than as a .docx attachment. Many systems strip attachments, and many more people have a (justifiable) allergy to opening attachments from an unknown source.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pete Storer | 2023-01-25 22:17:07 | FW: Query execution failure |
| Previous Message | Pete Storer | 2023-01-25 19:58:37 | Query execution failure |