- 20 4月, 2004 2 次提交
-
-
由 Bruce Momjian 提交于
o -Allow dump/load of CSV format This adds new keywords to COPY and \copy: CSV - enable CSV mode (comma separated variable) QUOTE - specify quote character ESCAPE - specify escape character FORCE - force quoting of specified column LITERAL - suppress null comparison for columns Doc changes included. Regression updates coming from Andrew.
-
由 Bruce Momjian 提交于
> o -Allow dump/load of CSV format
-
- 19 4月, 2004 2 次提交
-
-
由 Bruce Momjian 提交于
< * -Allow psql \du to show groups, and add \dg for groups > * -Allow psql \du to show users, and add \dg for groups
-
由 Tom Lane 提交于
are sought first as local FROM columns, then as local SELECT-list aliases, and finally as outer FROM columns; the former behavior made outer FROM columns take precedence over aliases. This does not change spec conformance because SQL99 allows only the first case anyway, and it seems more useful and self-consistent. Per gripe from Dennis Bjorklund 2004-04-05.
-
- 16 4月, 2004 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 15 4月, 2004 6 次提交
-
-
由 Tom Lane 提交于
RETURN NEXT.
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
< * Alvaro Herrera <alvherre@dcc.uchile.cl> > * Alvaro is Alvaro Herrera <alvherre@dcc.uchile.cl>
-
由 Bruce Momjian 提交于
< * Add the concept of dataspaces/tablespaces [tablespaces] > * Add the concept of dataspaces/tablespaces [tablespaces] (Gavin) 167c167 < * Allow savepoints / nested transactions [transactions] (Bruce) > * Allow savepoints / nested transactions [transactions] (Alvaro) 240c240 < o Allow Java server-side programming [java] > o Allow Java server-side programming [java] (Dave) 496a497 > * Alvaro Herrera <alvherre@dcc.uchile.cl>
-
- 13 4月, 2004 1 次提交
-
-
由 Bruce Momjian 提交于
It works on the principle of turning sockets into non-blocking, and then emulate blocking behaviour on top of that, while allowing signals to run. Signals are now implemented using an event instead of APCs, thus getting rid of the issue of APCs not being compatible with "old style" sockets functions. It also moves the win32 specific code away from pqsignal.h/c into port/win32, and also removes the "thread style workaround" of the APC issue previously in place. In order to make things work, a few things are also changed in pgstat.c: 1) There is now a separate pipe to the collector and the bufferer. This is required because the pipe will otherwise only be signalled in one of the processes when the postmaster goes down. The MS winsock code for select() must have some kind of workaround for this behaviour, but I have found no stable way of doing that. You really are not supposed to use the same socket from more than one process (unless you use WSADuplicateSocket(), in which case the docs specifically say that only one will be flagged). 2) The check for "postmaster death" is moved into a separate select() call after the main loop. The previous behaviour select():ed on the postmaster pipe, while later explicitly saying "we do NOT check for postmaster exit inside the loop". The issue was that the code relies on the same select() call seeing both the postmaster pipe *and* the pgstat pipe go away. This does not always happen, and it appears that useing WSAEventSelect() makes it even more common that it does not. Since it's only called when the process exits, I don't think using a separate select() call will have any significant impact on how the stats collector works. Magnus Hagander
-
- 12 4月, 2004 2 次提交
-
-
由 Bruce Momjian 提交于
Add pstdin/pstdout to read from psql's stdin/stdout. BACKWARD INCOMPATIBLE CHANGE
-
由 Bruce Momjian 提交于
> > pronouns and formatting in the Russian FAQ. Serguei Mokhov
-
- 11 4月, 2004 2 次提交
-
-
由 Bruce Momjian 提交于
calling proc_exit() directly. This should make SIGTERM more reliable.
-
由 Bruce Momjian 提交于
"millennium" date part implementation in postgresql, both in the code and the documentation, so that it conforms to the official definition. If you do not agree with the official definition, please send your complaint to "pope@vatican.org". I'm not responsible for them;-) With the previous version, the centuries and millenniums had a wrong number and started the wrong year. Moreover century number 0, which does not exist in reality, lasted 200 years. Also, millennium number 0 lasted 2000 years. If you want postgresql to have it's own definition of "century" and "millennium" that does not conform to the one of the society, just give them another name. I would suggest "pgCENTURY" and "pgMILLENNIUM";-) IMO, if someone may use the options, it means that postgresql is used for historical data, so it make sense to have an historical definition. Also, I just want to divide the year by 100 or 1000, I can do that quite easily. BACKWARD INCOMPATIBLE CHANGE Fabien Coelho - coelho@cri.ensmp.fr
-
- 10 4月, 2004 1 次提交
-
-
由 Bruce Momjian 提交于
gborg.
-
- 09 4月, 2004 3 次提交
-
-
由 Dennis Bjorklund 提交于
-
由 Dennis Bjorklund 提交于
-
由 Bruce Momjian 提交于
so remove regression result map line: horology/win32=horology-no-DST-before-1970
-
- 08 4月, 2004 11 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
< * Allow LOCALE on a per-column basis, default to ASCII > * Allow locale to be set at database creation > * Allow locale on a per-column basis, default to ASCII > * Optimize locale to have minimal performance impact when not used (Peter E) 105d106 < * Optimize locale to have minimal performance impact when not used (Peter E) 111d111 < * Allow locale to be set at database creation
-
由 Bruce Momjian 提交于
crash with debug in log_statement patch.
-
由 Tom Lane 提交于
Per example from Jiang Wei.
-
由 Bruce Momjian 提交于
> * Allow locale to be set at database creation
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
by the set operation, so that redundant sorts at higher levels can be avoided. This was foreseen a good while back, but not done. Per request from Karel Zak.
-
由 Tom Lane 提交于
causing it to fail to recognize the output ordering of subqueries that contain set operations (UNION/INTERSECT/EXPECT). Per example from Karel Zak.
-
由 Bruce Momjian 提交于
> * -Allow logging of only data definition(DDL), or DDL and modification statements Add: > * Add a session mode to warn about non-standard SQL usage
-
- 07 4月, 2004 5 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> >>with allowed values of "all, mod, ddl, none" with default "none". OK, here is a patch that implements #1. Here is sample output: test=> set client_min_messages = 'log'; SET test=> set log_statement = 'mod'; SET test=> select 1; ?column? ---------- 1 (1 row) test=> update test set x=1; LOG: statement: update test set x=1; ERROR: relation "test" does not exist test=> update test set x=1; LOG: statement: update test set x=1; ERROR: relation "test" does not exist test=> copy test from '/tmp/x'; LOG: statement: copy test from '/tmp/x'; ERROR: relation "test" does not exist test=> copy test to '/tmp/x'; ERROR: relation "test" does not exist test=> prepare xx as select 1; PREPARE test=> prepare xx as update x set y=1; LOG: statement: prepare xx as update x set y=1; ERROR: relation "x" does not exist test=> explain analyze select 1;; QUERY PLAN ------------------------------------------------------------------------------------ Result (cost=0.00..0.01 rows=1 width=0) (actual time=0.006..0.007 rows=1 loops=1) Total runtime: 0.046 ms (2 rows) test=> explain analyze update test set x=1; LOG: statement: explain analyze update test set x=1; ERROR: relation "test" does not exist test=> explain update test set x=1; ERROR: relation "test" does not exist It checks PREPARE and EXECUTE ANALYZE too. The log_statement values are 'none', 'mod', 'ddl', and 'all'. For 'all', it prints before the query is parsed, and for ddl/mod, it does it right after parsing using the node tag (or command tag for CREATE/ALTER/DROP), so any non-parse errors will print after the log line.
-
由 Tom Lane 提交于
That particular corner case is not exactly compelling, but given 7.4's ability to discard redundant join clauses, it is possible for the situation to arise from queries that are not so obviously silly. Per bug report of 6-Apr-04.
-
由 Tom Lane 提交于
equal to the desired restart value (must clear is_called, did not). Per bug report #1127 from Piotr Konieczny.
-
- 06 4月, 2004 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
the COPY NULL string: test=> copy pg_language to '/tmp/x' with delimiter '|'; COPY test=> copy pg_language to '/tmp/x' with delimiter '|' null '|x'; ERROR: COPY delimiter must not appear in the NULL specification test=> copy pg_language from '/tmp/x' with delimiter '|' null '|x'; ERROR: COPY delimiter must not appear in the NULL specification It also throws an error if it conflicts with the default NULL string: test=> copy pg_language to '/tmp/x' with delimiter '\\'; ERROR: COPY delimiter must not appear in the NULL specification test=> copy pg_language to '/tmp/x' with delimiter '\\' NULL 'x'; COPY
-
由 Bruce Momjian 提交于
-