Re: storing C binary array in bytea via libpq - Mailing list pgsql-general

From Tom DalPozzo
Subject Re: storing C binary array in bytea via libpq
Date
Msg-id CAK77FCQdbOJEyWU1QJtVYEiZJRhkzP=frUNc=kN-=OVopt5G1Q@mail.gmail.com
Whole thread Raw
In response to Re: storing C binary array in bytea via libpq  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [GENERAL] storing C binary array in bytea via libpq
List pgsql-general
Hi,
I tried both ways: they're ok.
Also, multiple VALUES in one INSERT is actually better as performance.

Thanks again
Pupillo



2016-12-06 19:49 GMT+01:00 Tom Lane <tgl@sss.pgh.pa.us>:
[ please keep the list cc'd ]

Tom DalPozzo <t.dalpozzo@gmail.com> writes:
> To be honest, I didn't know or I forgot about multiple VALUES in one
> command! Thanks for reminding!
> As for the PQexecParams, should I specify something in  const Oid
> *paramTypes parameter? Or just something like $1::bytea?

You can do it either way.  Hard-wiring the type OID will be a bit faster
than making the server parse a ton of repetitive cast constructs, but on
the other hand it means you have a magic number in your program.  It's
unlikely the OID assigned to bytea would ever change, but the technique
doesn't scale well to user-defined types.  Take your choice.

                        regards, tom lane

pgsql-general by date:

Previous
From: "Maeldron T."
Date:
Subject: Re: FreeBSD 10 => 11: Dump and reload your PostgreSQL database unless you like it broken
Next
From: Torsten Förtsch
Date:
Subject: high transaction rate