- 30 4月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 29 4月, 2003 1 次提交
-
-
由 Tom Lane 提交于
context sloppiness, some other things. Includes Neil's mopup patch of 22-Apr.
-
- 28 4月, 2003 8 次提交
-
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
than PQconnectdb. Reimplement the former to use the same code as the latter. Fix documentation omissions while at it.
-
由 Tom Lane 提交于
Linux man page for it. This error was preventing CVS tip from accepting remote connections.
-
由 Tom Lane 提交于
schema that was in our search path.
-
由 Tom Lane 提交于
declared without having to write %ROWTYPE. If the declared type of a variable is a composite type, it'll be taken to be a row variable automatically.
-
由 Tom Lane 提交于
I had inadvertently omitted it while rearranging things to support length-counted incoming messages. Also, change the parser's API back to accepting a 'char *' query string instead of 'StringInfo', as the latter wasn't buying us anything except overhead. (I think when I put it in I had some notion of making the parser API 8-bit-clean, but seeing that flex depends on null-terminated input, that's not really ever gonna happen.)
-
由 Tom Lane 提交于
test in there...
-
由 Tom Lane 提交于
in all cases, leaked TopMemoryContext memory in others. Make the interaction between SetClientEncoding and InitializeClientEncoding cleaner and better documented. I suspect these changes should be back-patched into 7.3, but will wait on Tatsuo's verification.
-
- 27 4月, 2003 2 次提交
- 26 4月, 2003 4 次提交
-
-
由 Tom Lane 提交于
new stats collector oftener than once a minute. Per gripe from Erik Walthinsen 4/25/03.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
initial values and runtime changes in selected parameters. This gets rid of the need for an initial 'select pg_client_encoding()' query in libpq, bringing us back to one message transmitted in each direction for a standard connection startup. To allow server version to be sent using the same GUC mechanism that handles other parameters, invent the concept of a never-settable GUC parameter: you can 'show server_version' but it's not settable by any GUC input source. Create 'lc_collate' and 'lc_ctype' never-settable parameters so that people can find out these settings without need for pg_controldata. (These side ideas were all discussed some time ago in pgsql-hackers, but not yet implemented.)
-
由 Bruce Momjian 提交于
-
- 25 4月, 2003 15 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
it, and map that to close() on Unix.
-
由 Tom Lane 提交于
into a UNION that has some type coercions applied to the component queries, so long as the qual itself does not reference any columns that have such coercions. Per example from Jonathan Bartlett 24-Apr-03.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
rewritten and the protocol is changed, but most elog calls are still elog calls. Also, we need to contemplate mechanisms for controlling all this functionality --- eg, how much stuff should appear in the postmaster log? And what API should libpq expose for it?
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Also update copyright to be ours, with approval from Jan.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 24 4月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
Karl Waclawek
-
- 23 4月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 22 4月, 2003 5 次提交
-
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
have length words. COPY OUT reimplemented per new protocol: it doesn't need \. anymore, thank goodness. COPY BINARY to/from frontend works, at least as far as the backend is concerned --- libpq's PQgetline API is not up to snuff, and will have to be replaced with something that is null-safe. libpq uses message length words for performance improvement (no cycles wasted rescanning long messages), but not yet for error recovery.
-
- 21 4月, 2003 2 次提交