- 03 5月, 2003 1 次提交
-
-
由 Tom Lane 提交于
Without this fix, CVS tip dumps core when running the regression tests with geqo_threshold = 2. I would think that a similar patch might be needed in 7.3, but cannot duplicate the failure in that branch --- so for now, leave well enough alone.
-
- 01 5月, 2003 1 次提交
-
-
由 Tom Lane 提交于
of extended query features in new FE/BE protocol. TransactionCommandContext is gone (PortalContext replaces it for some purposes), and QueryContext has taken on a new meaning (MessageContext plays its old role).
-
- 30 4月, 2003 1 次提交
-
-
由 Tom Lane 提交于
that the types of untyped string-literal constants are deduced (ie, when coerce_type is applied to 'em, that's what the type must be). Remove the ancient hack of storing the input Param-types array as a global variable, and put the info into ParseState instead. This touches a lot of files because of adjustment of routine parameter lists, but it's really not a large patch. Note: PREPARE statement still insists on exact specification of parameter types, but that could easily be relaxed now, if we wanted to do so.
-
- 29 4月, 2003 1 次提交
-
-
由 Tom Lane 提交于
context sloppiness, some other things. Includes Neil's mopup patch of 22-Apr.
-
- 28 4月, 2003 4 次提交
-
-
由 Tom Lane 提交于
schema that was in our search path.
-
由 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 3 次提交
-
-
由 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.)
-
- 25 4月, 2003 12 次提交
-
-
由 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 提交于
-
- 22 4月, 2003 2 次提交
-
-
由 Tom Lane 提交于
-
由 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 4 次提交
-
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
value, per recent discussion on pgsql-general.
-
由 Tom Lane 提交于
maintain a separate out-of-line version of PPC tas() anymore. Also fix S_UNLOCK for __powerpc64__ platforms.
-
由 Tom Lane 提交于
deferredTriggerInvokeEvents only scan events added since it last ran. Stephan Szabo, some corrections by Tom Lane.
-
- 20 4月, 2003 2 次提交
-
-
由 Bruce Momjian 提交于
Output \r\n termination on Win32. Disallow literal carriage return as a data value, backslash-carriage-return and \r still allowed. Doc changes already committed.
-
由 Bruce Momjian 提交于
-
- 19 4月, 2003 2 次提交
- 18 4月, 2003 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
with variable-width fields. No more truncation of long user names. Also, libpq can now send its environment-variable-driven SET commands as part of the startup packet, saving round trips to server.
-
- 16 4月, 2003 1 次提交
-
-
由 Tom Lane 提交于
-
- 15 4月, 2003 2 次提交
-
-
由 Tom Lane 提交于
account for NULLs; in hindsight this is obvious since the code for the MCV-lists case would reduce to this when there are zero entries in both lists. Per example from Alec Mitchell.
-
由 Tom Lane 提交于
be reduced to a plain ERROR. Should make it at least a little less painful to deal with data-corruption problems.
-