[HACKERS] Modifing returning value of PQgetvalue.

Hello, PQgetvalue returns a value of type char* (without const). But the documentation says: "The pointer returned by PQgetvalue points to storage that is part of the PGresult structure. *One should not modify the data it points to*" (my italics). Could someone tell me please, what wrong with

Re: [HACKERS] [GENERAL] C++ port of Postgres

2016-08-17 14:40 GMT+03:00 Aleksander Alekseev : >> I'm sure this wasn't your intent, but the tone of your response is >> part of why people don't get involved with Postgres development... >> >> Please note that you're the only person in the entire thread that's >> said

Re: [HACKERS] [GENERAL] C++ port of Postgres

2016-08-16 18:52 GMT+03:00 Heikki Linnakangas : > On 08/16/2016 05:47 PM, Jim Nasby wrote: >> >> I realize there's little technical reason why we *need* C++ support. The >> level if discipline applied to our codebase negates some of the benefits >> of C++. But maintaining the

Re: [HACKERS] PATCH: Batch/pipelining support for libpq

2016-05-24 5:01 GMT+03:00 Craig Ringer : > > On 24 May 2016 at 00:00, Michael Paquier wrote: >> >> On Mon, May 23, 2016 at 8:50 AM, Andres Freund wrote: > > >> >> > yay^2. >> >> I'll follow this mood. Yeha. > > > > BTW, I've

Re: [HACKERS] Deleting prepared statements from libpq.

2016-05-25 16:50 GMT+03:00 Tom Lane <t...@sss.pgh.pa.us>: > Dmitry Igrishin <dmit...@gmail.com> writes: > > "there is no libpq function for deleting a prepared statement". > > Could you tell me please, what is the reason for this? > > You don't really

[HACKERS] Deleting prepared statements from libpq.

Hello, According to https://www.postgresql.org/docs/current/static/protocol-flow.html#PROTOCOL-FLOW-EXT-QUERY there are Close message for closing prepared statements or portals, but according to https://www.postgresql.org/docs/current/static/libpq-exec.html#LIBPQ-PQPREPARE "there is no libpq

Re: [HACKERS] SET SESSION AUTHORIZATION superuser limitation.

2015-12-21 17:57 GMT+03:00 Tom Lane : > Robert Haas writes: > > On Sun, Dec 20, 2015 at 1:47 PM, Tom Lane wrote: > >> The syntax you propose exposes the user's password in cleartext in > >> the command, where it is likely to get

[HACKERS] SET SESSION AUTHORIZATION superuser limitation.

Hackers, There are feature which may be useful in conjunction with connection pools. It is the ability to change the session user without creating the new connection, like this: (pseudo REPL): notsuperuser > SELECT current_user, session_user; notsuperuser notsuperuser notsuperuser > SET SESSION

Re: [HACKERS] SET SESSION AUTHORIZATION superuser limitation.

2015-12-20 21:47 GMT+03:00 Tom Lane <t...@sss.pgh.pa.us>: > Dmitry Igrishin <dmit...@gmail.com> writes: > > There are feature which may be useful in conjunction with connection > pools. > > It is the ability to change the session user without creatin

Re: [HACKERS] How to create shared_ptr for PGconn?

2015-03-16 19:32 GMT+03:00 Chengyu Fan chengyu@hotmail.com: Hi, Does anyone know how to create the shared_ptr for PGconn? I always get compile errors ... Below is my code: --- const char * dbInfo = xxx; PGconn *conn = PGconnectdb(dbInfo); if (PGstatus(conn) !=