Re: BUG #18774: Not the required output of the query used in the function(delete_from_table1) in postgresql9.4

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Vik Fearing <vik(at)postgresfriends(dot)org>
Cc: Rajni Bobal <rajnibobal(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18774: Not the required output of the query used in the function(delete_from_table1) in postgresql9.4
Date: 2025-01-16 15:58:28
Message-ID: 1623377.1737043108@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Vik Fearing <vik(at)postgresfriends(dot)org> writes:
> #18776 appears to have been discarded as a duplicate.  In any case, no
> one is going to fix a bug in 9.4 which has been EOL since 2020.  I
> suggest you upgrade to a supported version and re-report the bug if it
> still exists.

If you do reproduce your problem on a still-in-support branch,
please re-file with a *self-contained* test case. It's impossible
for someone to reverse-engineer your problem from just the two
function definitions, with no table declarations, sample data,
calling sequence, or expected vs. actual results.

https://wiki.postgresql.org/wiki/Guide_to_reporting_problems

If it's difficult to cram all the details into our bug-reporting
form, personally I'd ignore the form and just send mail to
pgsql-bugs(at)lists(dot)postgresql(dot)org

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2025-01-16 16:02:59 Re: BUG #18775: PQgetCopyData always has an out-of-memory error if the table field stores bytea ~700 MB
Previous Message Vik Fearing 2025-01-16 14:55:25 Re: BUG #18774: Not the required output of the query used in the function(delete_from_table1) in postgresql9.4