| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | kirankhatke23may(at)gmail(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16007: Regarding patch for BUG #3995: pqSocketCheck doesn't return |
| Date: | 2019-09-12 20:17:34 |
| Message-ID: | 27311.1568319454@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:
> We are using PostgreSQL Version 8.3.17 in our product and running into issue
> described under BUG#3995.
> Can you please share if any patch is there on 8.3.x version to address this
> issue.
So far as I can see from the discussion of #3995, there was absolutely
no reason to think there was any PG bug. But you are following in the
footsteps of that reporter by (a) jumping to a conclusion about what
your problem is, and (b) providing absolutely zero concrete information
that would allow anyone to help you.
Please read
https://wiki.postgresql.org/wiki/Guide_to_reporting_problems
Also, you really should think about updating to a version of Postgres
that isn't many years obsolete. Even if your problem did trace down
to being a PG bug, we are not going to fix it in 8.3.x.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-09-12 20:33:55 | Re: BUG #16006: Update queries fail on a table having any policy with a function that takes a whole-row var as arg |
| Previous Message | PG Bug reporting form | 2019-09-12 19:51:52 | BUG #16007: Regarding patch for BUG #3995: pqSocketCheck doesn't return |