- 29 7月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
materialized. New items have been added to GucContext and GucSource enums, but of course they were not added to the corresponding GucContextName[] and GucSourceName[] arrays in the patch. Here's a new patch to fix the resulting bugs. Joe Conway
-
- 28 7月, 2003 3 次提交
- 27 7月, 2003 2 次提交
-
-
由 Tom Lane 提交于
the bulk of the heavy lifting ...
-
由 Bruce Momjian 提交于
>>ISTM that "source" is worth knowing. > > Hm, possibly. Any other opinions? This version has the seven fields I proposed, including "source". Here's an example that shows why I think it's valuable: regression=# \x Expanded display is on. regression=# select * from pg_settings where name = 'enable_seqscan'; -[ RECORD 1 ]----------- name | enable_seqscan setting | on context | user vartype | bool source | default min_val | max_val | regression=# update pg_settings set setting = 'off' where name = 'enable_seqscan'; -[ RECORD 1 ]--- set_config | off regression=# select * from pg_settings where name = 'enable_seqscan'; -[ RECORD 1 ]----------- name | enable_seqscan setting | off context | user vartype | bool source | session min_val | max_val | regression=# alter user postgres set enable_seqscan to 'off'; ALTER USER (log out and then back in again) regression=# \x Expanded display is on. regression=# select * from pg_settings where name = 'enable_seqscan'; -[ RECORD 1 ]----------- name | enable_seqscan setting | off context | user vartype | bool source | user min_val | max_val | In the first case, enable_seqscan is set to its default value. After setting it to off, it is obvious that the value has been changed for the session only. In the third case, you can see that the value has been set specifically for the user. Joe Conway
-
- 26 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
-
- 25 7月, 2003 2 次提交
- 24 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
was modified for IPv6. Use a robust definition of struct sockaddr_storage, do a proper configure test to see if ss_len exists, don't assume that getnameinfo() will handle AF_UNIX sockets, don't trust getaddrinfo to return the protocol we ask for, etc. This incorporates several outstanding patches from Kurt Roeckx, but I'm to blame for anything that doesn't work ...
-
- 23 7月, 2003 3 次提交
-
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
Along the way, fix some logic problems in pgstat_initstats, notably the bogus assumption that malloc returns zeroed memory.
-
- 22 7月, 2003 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
- 21 7月, 2003 2 次提交
- 20 7月, 2003 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
- 19 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
-
- 18 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
date2j(). This ensures we give reasonable errors instead of bizarre behavior for input dates far in the future.
-
- 17 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
for the sign of timezone offsets, ie, positive is east from UTC. These were previously out of step with other operations that accept or show timezones, such as I/O of timestamptz values.
-
- 16 7月, 2003 2 次提交
- 15 7月, 2003 4 次提交
- 10 7月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
Aizaz Ahmed
-
- 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.
-
- 04 7月, 2003 3 次提交
-
-
由 Tom Lane 提交于
function-not-found messages now distinguish the cases no-match and ambiguous-match, and they follow the style guidelines too.
-
由 Tom Lane 提交于
instead of the former kluge whereby gram.y emitted already-transformed expressions. This is needed so that Params appearing in these clauses actually work correctly. I suppose some might claim that the side effect of 'SELECT ... LIMIT 2+2' working is a new feature, but I say this is a bug fix.
-
由 Tom Lane 提交于
so it has some chance of working in rules ...
-
- 02 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
It also works to create a non-polymorphic aggregate from polymorphic functions, should you want to do that. Regression test added, docs still lacking. By Joe Conway, with some kibitzing from Tom Lane.
-
- 01 7月, 2003 2 次提交
-
-
由 Tom Lane 提交于
ANYELEMENT. The effect is to postpone typechecking of the function body until runtime. Documentation is still lacking. Original patch by Joe Conway, modified to postpone type checking by Tom Lane.
-
由 Tom Lane 提交于
reports get put into the postmaster log. Options are TERSE, DEFAULT, VERBOSE, with the same behavior as implemented on the client side in libpq.
-
- 30 6月, 2003 1 次提交
-
-
由 Tom Lane 提交于
node emits only those vars that are actually needed above it in the plan tree. (There were comments in the code suggesting that this was done at some point in the dim past, but for a long time we have just made join nodes emit everything that either input emitted.) Aside from being marginally more efficient, this fixes the problem noted by Peter Eisentraut where a join above an IN-implemented-as-join might fail, because the subplan targetlist constructed in the latter case didn't meet the expectation of including everything. Along the way, fix some places that were O(N^2) in the targetlist length. This is not all the trouble spots for wide queries by any means, but it's a step forward.
-
- 29 6月, 2003 1 次提交
-
-
由 Tom Lane 提交于
'scalar op ALL (array)', where the operator is applied between the lefthand scalar and each element of the array. The operator must yield boolean; the result of the construct is the OR or AND of the per-element results, respectively. Original coding by Joe Conway, after an idea of Peter's. Rewritten by Tom to keep the implementation strictly separate from subqueries.
-