| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
| Cc: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: extended query protcol violation? |
| Date: | 2018-12-08 13:36:08 |
| Message-ID: | CADK3HHJ8D-ZcOsRW58Y+AwRq7YnRs_h01e=SDPK4wby5GBUGJA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, 8 Dec 2018 at 08:18, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> wrote:
> >> > Curious what client is this that is violating the protocol.
> >>
> >> I heard it was a Java program.
> >>
> >
> > This is not surprising there are a proliferation of non-blocking
> > implementations,
> > probably approaching 10 different implementations now.
>
> Do you think some of the implementations may not be appropriate if
> they behave like that discussed in this thread? If so, maybe it is
> worth to add a warning to the backend.
>
Given that java code is notorious for not reading warnings, I'd say no
That said I'd probably be in favour of a DEBUG mode that did warn.
Dave Cramer
davec(at)postgresintl(dot)com
www.postgresintl.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2018-12-08 13:36:38 | Re: COPY FROM WHEN condition |
| Previous Message | Tatsuo Ishii | 2018-12-08 13:18:38 | Re: extended query protcol violation? |