packets data - Search results in mailing lists
Mailing lists >> pgsql-interfaces >> Thread
2015-03-03 19:47:14 | Re: libpq connect keepalive* parms: no effect!? (Bill Clay)
packet retransmission limit. Presently for Linux, the default value for this parameter (sysctl parameter net.ipv4.tcp_retries2) is 15. Linux TCP spaces these retries nearly exponentially: the first retry is subsecond, and subsequent retries
Mailing lists >> pgsql-interfaces >> Thread
2014-08-12 20:18:39 | Re: Protocol Question (Thomas Heller)
packets to minimize network overhead." If I skip the Flush after Execute I receive no data
Mailing lists >> pgsql-interfaces >> Thread
2005-11-03 11:25:18 | error encountered in windows when libpq sends large query string to server (Ranen Ghosh)
data to server: No buffer space available (0x00002747/10055) from postgresql-8.0.3/src/interfaces/libpq/win32.c: WSAENOBUFS, "No buffer space available" from http:///library/default.asp?url=/library/en-us/winsock/winsock/windows_sockets_error_codes_2.asp: WSAENOBUFS 10055 The problem is client side: when a smaller query string is successfully sent
Mailing lists >> pgsql-interfaces >> Thread
2004-11-14 08:09:32 | about libpq-C FETCH performance issue (jing han)
data from database to send out ip packets at fast rate. With libpq-C interface
Mailing lists >> pgsql-interfaces >> Thread
2004-11-14 05:27:56 | about libpq-C FETCH ALL performance issue (jing han)
data from database and send them out as ip packets. With libpq-C interface, I have
Mailing lists >> pgsql-interfaces >> Thread
2004-07-07 22:14:01 | Re: pgin.tcl pg_exec_prepared slow (was: Released...) (L J Bayuk)
data when control returns to the main loop. But it..." I could not find the described flush "when control returns to the main loop". Either I'm missing it, or it isn't there
Mailing lists >> pgsql-interfaces >> Thread >> Search in thread (2)
2003-04-20 20:20:33 | FE/BE Protocol 3.0 Draft - Some Comments (ljb)
data to the backend (without having to escape it)? Is there some other way than FunctionCall? How would the large object interface work without FunctionCall? 3) There is still no way to pass NULL
Mailing lists >> pgsql-interfaces >> Thread
2003-03-10 13:51:23 | Roadmap for FE/BE protocol redesign (Tom Lane)
data (any ideas?) to frontend during startup, to avoid need for explicit queries to get this info. We could also consider eliminating SET commands sent by libpq in favor of adding variable settings to startup
Mailing lists >> pgsql-interfaces >> Thread >> Search in thread (2)
2001-06-04 16:10:56 | Re: libpq sockets on win32 (Bruce Momjian)
packet: " "errno=%d\n%s\n", ! sockerrno, strerror(sockerrno)); goto error_return; } *************** *** 2110,2116 **** --- 2106,2114 ---- int PQrequestCancel(PGconn *conn) { + #ifndef WIN32 int save_errno = errno; + #endif int tmpsock = -1; struct
Mailing lists >> pgsql-interfaces >> Thread
2000-10-06 18:24:38 | C++ interfaces (Randy Jonasz)
packet which sends the backend key data. Every time I have psql connect to postmaster
Mailing lists >> pgsql-interfaces >> Thread
1999-12-10 02:42:57 | RE: [INTERFACES] Large Object Exception/Serializing Java Objects (Peter Mount)
packet labeled Z, so added a check for it. Peter -- Peter Mount Enterprise Support Maidstone Borough Council Any views stated are my own, and not those of Maidstone Borough Council. -----Original Message----- From: Joe Shevland
Mailing lists >> pgsql-interfaces >> Thread
1999-10-02 21:45:47 | Re: [INTERFACES] timeouts in libpq- can libpq requests block forever/a very long time? (Dirk Niggemann)
data over it. c) shoot router by preferred method (ax, fire, power plug, admin typo, dripping aircon (my favourite)).d) see how long your socket connection takes to work out the network's gone away
Mailing lists >> pgsql-interfaces >> Thread
1999-10-01 15:55:46 | Problems with large objects and 6.51 (Wolfgang Hottgenroth)
data, we have to release the partially * constructed PGresult, and rebuild it again next time. Fortunately, * that shouldn't happen often, since 'T' messages usually fit in a packet
Mailing lists >> pgsql-interfaces >> Thread
1999-08-27 13:20:42 | problems with large objects (Wolfgang Hottgenroth)
data, we have to release the partially * constructed PGresult, and rebuild it again next time. Fortunately, * that shouldn't happen often, since 'T' messages usually fit in a packet
Mailing lists >> pgsql-interfaces >> Thread
1999-07-22 17:11:33 | Frontend/Backend Protocol (Jonathan Dale)
packet, which consists of: 00 00 01 20 as the length (296 bytes) 00 02 00 00 as the major and minor protocol numbers (2.0) "dbname\0" as a 64 byte string representing the database