| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, tharakan(at)gmail(dot)com, PostgreSQL Bugs List <pgsql-bugs(at)postgresql(dot)org>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [BUGS] pgbench -C -M prepared gives an error |
| Date: | 2016-03-17 07:57:24 |
| Message-ID: | alpine.DEB.2.10.1603170853230.22499@sto |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Hello Tatsuo,
>> We're not resetting the prepared[] array when we pull the plug on an
>> existing connection.
>>
>> Is a connection per transaction really a sane case to consider?
>
> Yes, I would think. This case reveals the connection overhead. We
> already are able to handle the simple query cases. Why not for
> extended query cases?
Probably it can be made to work, but it is much less useful to prepare a
statement which is known to be needed just once, so I think it would be
fine to simply forbid "-M prepared" and "-C" together.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-03-17 13:14:58 | Re: [HACKERS] pgbench -C -M prepared gives an error |
| Previous Message | Thomas Munro | 2016-03-17 03:14:22 | Re: to_char(OF) is broken |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Petr Jelinek | 2016-03-17 08:01:26 | Re: Relation extension scalability |
| Previous Message | Petr Jelinek | 2016-03-17 07:56:49 | Re: WIP: Access method extendability |