- 13 1月, 2003 3 次提交
-
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
-
- 12 1月, 2003 9 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
more to be done yet, but this is a good start.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
supported.
-
由 Tom Lane 提交于
direction on HP-UX; our former approach has been obsolete since HPUX 9. Giles Lean
-
由 Bruce Momjian 提交于
-
- 11 1月, 2003 11 次提交
-
-
由 Tatsuo Ishii 提交于
-
由 Bruce Momjian 提交于
> > I'd suggest that the runtime.sgml description explicitly say "values of > at least a few thousand are recommended for production installations". Neil Conway
-
由 Bruce Momjian 提交于
Manfred Koizar
-
由 Bruce Momjian 提交于
RELEASE_CHANGES. Manfred Koizar
-
由 Bruce Momjian 提交于
SET_TRANSACTION.
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
shared by nodeGroup, nodeAgg, and soon nodeSubplan.
-
由 Tom Lane 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
command with arguments.
-
由 Tom Lane 提交于
Simplify SubLink by storing just a List of operator OIDs, instead of a list of incomplete OpExprs --- that was a bizarre and bulky choice, with no redeeming social value since we have to build new OpExprs anyway when forming the plan tree.
-
- 10 1月, 2003 5 次提交
-
-
由 Peter Eisentraut 提交于
Currently, only RESTRICT is allowed.
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
'NOT (x IN (subselect))', that is 'NOT (x = ANY (subselect))', rather than 'x <> ALL (subselect)' as we formerly did. This opens the door to optimizing NOT IN the same way as IN, whereas there's no hope of optimizing the expression using <>. Also, convert 'x <> ALL (subselect)' to the NOT(IN) style, so that the optimization will be available when processing rules dumped by older Postgres versions. initdb forced due to small change in SubLink node representation.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
by having to include miscadmin.h into other header files.
-
- 09 1月, 2003 12 次提交
-
-
由 Peter Eisentraut 提交于
interfaces.
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
per gripe from Csaba Nagy. There is still potential for platform-specific behavior for values that are exactly halfway between integers, but at least we now get the expected answer for all other cases.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
causes interval rounding not to work as expected in 7.3, for example SELECT '18:17:15.6'::interval(0) does not round the value. I did not force initdb, but one is needed to install the added row.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
believe I didn't notice this before -- once 64k was sent to/from the server the client would crash. Basicly, in 7.3 the server SSL code set the initial state to "about to renegotiate" without actually starting the renegotiation. In addition, the server and client didn't properly handle the SSL_ERROR_WANT_(READ|WRITE) error. This is fixed in the second patch. Nathan Mueller
-
由 Bruce Momjian 提交于
first, that I missed when checking over 7.3.1, was that the client method was switched to SSLv23 along with the server. The SSLv23 client method does SSLv2 by default, but can also understand SSLv3. In our situation the SSLv2 backwords compatibility is really only needed on the server. This is the first patch. The last thing is that I found a way for the server to understand SSLv2 HELLO messages (sent by pre-7.3 clients) but then get them to talk SSLv3. This is the last one. Nathan Mueller
-
由 Bruce Momjian 提交于
> The big problem is that while pg_dump's dump_trigger() looks at > tginitdeferred and dumps accordingly, pg_get_constraintdef doesn't look > at tginitdeferred, and therefore doesn't record the requirement as part > of ALTER TABLE ADD CONSTRAINT. pg_get_constraintdef should probably be looking at condeferrable and condeferred in the pg_constraint row it's looking at. Maybe something like the attached. (Added, output only non-default values.) Stephan Szabo
-