- 01 9月, 2002 6 次提交
-
-
由 Bruce Momjian 提交于
> o -SELECT col FROM tab WHERE numeric_col = 10.1 fails, requires quotes
-
由 Tom Lane 提交于
pointed out by Barry Lind: UPDATE bigintcol = 10000000000 fails because the constant is initially taken as float8. We really need a better way, but it's not gonna happen for 7.3. Also, remove int4reltime() function, which is redundant with the existing binary-compatibility coercion path from int4 to reltime, and probably has been unreachable code for a long while.
-
由 Tom Lane 提交于
type for runtime constraint checks, instead of misusing the parse-time Constraint node for the purpose. Fix some damage introduced into type coercion logic; in particular ensure that a coerced expression tree will read out the correct result type when inspected (patch had broken some RelabelType cases). Enforce domain NOT NULL constraints against columns that are omitted from an INSERT.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
you try to use the tupdesc to build a tuple. Joe Conway
-
由 Tom Lane 提交于
available (else there's no way to interpret the list links). Change pg_locks view to show transaction ID locks separately from ordinary relation locks. Avoid showing N duplicate rows when the same lock is held multiple times (seems unlikely that users care about exact hold count). Improve documentation.
-
- 31 8月, 2002 15 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
functions, per suggestion from John Gray and Joe Conway. Also, fix plpgsql RETURN NEXT to verify that returned values match the expected tupdesc.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
to false provides more SQL-spec-compliant behavior than we had before. I am not sure that setting it false is actually a good idea yet; there is a lot of client-side code that will probably be broken by turning autocommit off. But it's a start. Loosely based on a patch by David Van Wie.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
column additions, deletions, and renames that would let a child table get out of sync with its parent. Patch by Alvaro Herrera, with some kibitzing by Tom Lane.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
* Remove wal_files postgresql.conf option because WAL files are now recycled
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Improve wording of pre-7.3 syntax mention.
-
- 30 8月, 2002 19 次提交
-
-
由 Marc G. Fournier 提交于
perl5 interface moved to gborg
-
由 Marc G. Fournier 提交于
libpgeasy moved to gborg ...
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
at least not on HPUX 10.20, and there's no reason to think it is needed on later versions.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
which is now required.
-
由 Tom Lane 提交于
that the functionality is available to anyone via ReturnSetInfo, rather than hard-wiring it to PL/pgSQL.
-
由 Hiroshi Inoue 提交于
-
由 Bruce Momjian 提交于
> > > > where is the code to verify that PGPASSWORDFILE points at a > > > > non-world-readable file? That needs to be there now, not later, or > > > > we'll have people moaning about backward compatibility when we finally > > > > do plug that hole. Alvaro Herrera
-
由 Bruce Momjian 提交于
> Upon invoking a polygon(integer, circle) function a > src/backend/utils/adt/geo_ops.c:circle_poly() function will gets > called, which suffers from a buffer overflow. > > 2) A src/backend/adt/utils/geo_ops.c:path_encode() fails to detect a > buffer overrun condition. It is called in multiple places, the most > interesting are path_out() and poly_out() functions. > 5) A src/backend/utils/adt/geo_ops.c:path_add() also fails to detect > a simple buffer overrun. I've attached a patch which should fix these problems. Neil Conway
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
diffs to 7.3-devel and may not be applicable to 7.2. I have included a change covered by a previous bugfix patch I submitted (the problem with -.1 not being accepted by cube_in). It does not include a fix for the potential buffer overrun issue I reported for cube_yyerror in cubeparse.y. Bruno Wolff III
-
由 Peter Eisentraut 提交于
translation.
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
memory. Neil Conway
-
由 Bruce Momjian 提交于
connections by the superuser only. This patch replaces the last patch I sent a couple of days ago. It closes a connection that has not been authorised by a superuser if it would leave less than the GUC variable ReservedBackends (superuser_reserved_connections in postgres.conf) backend process slots free in the SISeg. This differs to the first patch which only reserved the last ReservedBackends slots in the procState array. This has made the free slot test more expensive due to the use of a lock. After thinking about a comment on the first patch I've also made it a fatal error if the number of reserved slots is not less than the maximum number of connections. Nigel J. Andrews
-
由 Bruce Momjian 提交于
please apply small patch for README.tsearch. I've documented space usage and using CLUSTER command Oleg Bartunov
-