Re: PATCH: Batch/pipelining support for libpq - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: PATCH: Batch/pipelining support for libpq
Date
Msg-id CAMsr+YGY7CO8+vWBqFfdYLqzrZSpcKHc-AVWSu25_++kek-Ecw@mail.gmail.com
Whole thread Raw
In response to Re: PATCH: Batch/pipelining support for libpq  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: PATCH: Batch/pipelining support for libpq  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 24 May 2016 at 00:00, Michael Paquier <michael.paquier@gmail.com> wrote:
 

Did you consider the use of simple_list.c instead of introducing a new
mimic as PGcommandQueueEntry? It would be cool avoiding adding new
list emulations on frontends.

I'd have to extend simple_list to add a generic object version, like


struct my_list_elem
{
    PG_SIMPLE_LIST_ATTRS;
    mytype mycol;
    myothertype myothercol;

Objections?

I could add a void* version that's a simple clone of the string version, but having to malloc both a list cell and its contents separately is annoying.

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: BTREE_BUILD_STATS build is broken
Next
From: Tom Lane
Date:
Subject: Re: PATCH: Batch/pipelining support for libpq