- 07 8月, 2003 1 次提交
-
-
由 Tom Lane 提交于
macros in some platforms' sys/socket.h.
-
- 04 8月, 2003 3 次提交
-
-
由 Tom Lane 提交于
and seems to have too few users to justify maintaining.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 29 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
heuristic determination of day vs month in date/time input. Add the ability to specify that input is interpreted as yy-mm-dd order (which formerly worked, but only for yy greater than 31). DateStyle's input component now has the preferred spellings DMY, MDY, or YMD; the older keywords European and US are now aliases for the first two of these. Per recent discussions on pgsql-general.
-
- 28 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
-
- 23 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
Along the way, fix some logic problems in pgstat_initstats, notably the bogus assumption that malloc returns zeroed memory.
-
- 09 7月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
or increased only by super-users. This fixes problems caused by making certain variables SUSET for security reasons.
-
- 05 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
without needing a running backend. Reorder postgresql.conf.sample to match new layout of runtime.sgml. This commit re-adds work lost in Wednesday's crash.
-
- 21 6月, 2003 1 次提交
-
-
由 Tom Lane 提交于
a ReadyForQuery (Z message) immediately and then another one after the Sync message arrives. Suppress the first one to make it work per spec.
-
- 12 6月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
Christopher Kings-Lynne
-
- 28 5月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
docs that CLIENT/LOG_MIN_MESSAGES now controls debug_* output location. Doc changes included.
-
- 15 5月, 2003 1 次提交
-
-
由 Tom Lane 提交于
-
- 14 5月, 2003 1 次提交
-
-
由 Tom Lane 提交于
only remnant of this failed experiment is that the server will take SET AUTOCOMMIT TO ON. Still TODO: provide some client-side autocommit logic in libpq.
-
- 13 5月, 2003 1 次提交
-
-
由 Tom Lane 提交于
efficient insertion of large bytea values through the BIND interface.
-
- 10 5月, 2003 1 次提交
-
-
由 Tom Lane 提交于
messages. Binary I/O is now up and working, but only for a small set of datatypes (integers, text, bytea).
-
- 09 5月, 2003 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
handle multiple 'formats' for data I/O. Restructure CommandDest and DestReceiver stuff one more time (it's finally starting to look a bit clean though). Code now matches latest 3.0 protocol document as far as message formats go --- but there is no support for binary I/O yet.
-
- 08 5月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
Allow backends to attached to specified shared memory address.
-
- 07 5月, 2003 3 次提交
-
-
由 Bruce Momjian 提交于
fork/exec.
-
由 Tom Lane 提交于
of Describe on a prepared statement. This was in the original 3.0 protocol proposal, but I took it out for reasons that seemed good at the time. Put it back per yesterday's pghackers discussion.
-
由 Tom Lane 提交于
DestReceiver pointers instead of just CommandDest values. The DestReceiver is made at the point where the destination is selected, rather than deep inside the executor. This cleans up the original kluge implementation of tstoreReceiver.c, and makes it easy to support retrieving results from utility statements inside portals. Thus, you can now do fun things like Bind and Execute a FETCH or EXPLAIN command, and it'll all work as expected (e.g., you can Describe the portal, or use Execute's count parameter to suspend the output partway through). Implementation involves stuffing the utility command's output into a Tuplestore, which would be kind of annoying for huge output sets, but should be quite acceptable for typical uses of utility commands.
-
- 06 5月, 2003 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Reorder non-default variable loading until PGDATA is defined.
-
由 Tom Lane 提交于
the column by table OID and column number, if it's a simple column reference. Along the way, get rid of reskey/reskeyop fields in Resdoms. Turns out that representation was not convenient for either the planner or the executor; we can make the planner deliver exactly what the executor wants with no more effort. initdb forced due to change in stored rule representation.
-
- 05 5月, 2003 1 次提交
-
-
由 Tom Lane 提交于
Only lightly tested as yet, since libpq doesn't know anything about 'em.
-
- 03 5月, 2003 5 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
Both plannable queries and utility commands are now always executed within Portals, which have been revamped so that they can handle the load (they used to be good only for single SELECT queries). Restructure code to push command-completion-tag selection logic out of postgres.c, so that it won't have to be duplicated between simple and extended queries. initdb forced due to addition of a field to Query nodes.
-
- 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.
-
- 28 4月, 2003 1 次提交
-
-
由 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.)
-
- 25 4月, 2003 1 次提交
-
-
由 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?
-
- 22 4月, 2003 1 次提交
-
-
由 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.
-
- 19 4月, 2003 1 次提交
-
-
由 Tom Lane 提交于
have length counts, and COPY IN data is packetized into messages.
-
- 18 4月, 2003 1 次提交
-
-
由 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.
-
- 25 3月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
when autocommit is off, and document grouping when autocommit is on.
-
- 22 3月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
Cleans up blank query handling to be more consistent.
-
- 20 3月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
Add ALTER SEQUENCE to modify min/max/increment/cache/cycle values Also updated create sequence docs to mention NO MINVALUE, & NO MAXVALUE. New Files: doc/src/sgml/ref/alter_sequence.sgml src/test/regress/expected/sequence.out src/test/regress/sql/sequence.sql ALTER SEQUENCE is NOT transactional. It behaves similarly to setval(). It matches the proposed SQL200N spec, as well as Oracle in most ways -- Oracle lacks RESTART WITH for some strange reason. -- Rod Taylor <rbt@rbt.ca>
-