- 04 8月, 2002 17 次提交
-
-
由 Tom Lane 提交于
Which was true when he submitted it, but is so no longer.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> please find attached patch to current CVS ( contrib/ltree) > Version for 7.2 is distributed as separate package - I believe that patch also intended to remove contrib/ltree/patch.72
-
由 Bruce Momjian 提交于
Please use this patch instead of my previously submitted one. It is just remerged against HEAD for new alter_table.out stuff. Another reason this patch is useful for _interactive_ users: imagine a view based on a many way join. Imagine creating a complicated insert rule that inserts into all the joined tables and when you insert you get a check failure, but you need to know which actual table the constraint was on that failed! Christopher Kings-Lynne
-
由 Bruce Momjian 提交于
the statistics collector and makes a number of corrections to the documentation for SET, SHOW, and COPY. Neil Conway
-
由 Bruce Momjian 提交于
ERROR: ExecInsert: rejected due to CHECK constraint insert_con To be like this: ERROR: ExecInsert: rejected due to CHECK constraint "insert_con" on "insert_tbl" Updated regression tests to match. I got sick of seeing 'rejected due to CHECK constraint "$1" in my log and not being able to find the bug in our website code... Christopher Kings-Lynne
-
由 Bruce Momjian 提交于
Neil Conway
-
由 Bruce Momjian 提交于
Changes: July 31, 2002 Now works on 64-bit platforms. Added function lca - lowest common ancestor Version for 7.2 is distributed as separate package - http://www.sai.msu.su/~megera/postgres/gist/ltree/ltree-7.2.tar.gz Oleg Bartunov
-
由 Bruce Momjian 提交于
when compiling psql with GCC 3.1. Neil Conway
-
由 Bruce Momjian 提交于
functionality of the command is basically identical to that of BEGIN; it just accepts a few extra options (only one of which PostgreSQL currently implements), and is standards-compliant. The patch includes a simple regression test and documentation. [ Regression tests removed, per Peter.] Neil Conway
-
由 Bruce Momjian 提交于
there was a race condition between the "alter_table" and "rules" regression tests. Depending on scheduling, sometimes an ALTER TABLE command would operate on a relation created by the "rules" tests, leading to unexpected results. Neil Conway
-
由 Bruce Momjian 提交于
Neil Conway
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
whitespaces in identifers of any kind(table names,attribute names,variables ...) in Pl/pgSQL procedural language.Explicit definition of bug can be found in Re: [HACKERS] Bug of PL/pgSQL parser TODO item completed: o -Fix PL/PgSQL to handle quoted mixed-case identifiers eutm
-
由 Bruce Momjian 提交于
functions. If there are no objections, please apply. Joe Conway
-
- 03 8月, 2002 6 次提交
-
-
由 Tom Lane 提交于
in the relcache. It's rather silly that we have reference count leak checks in bufmgr and in catcache, but not in relcache which will normally have many fewer entries. Chris K-L would have caught at least one bug in his recent DROP patch if he'd had this.
-
由 Tom Lane 提交于
relation being modified. In most paths of control we'd already have such a lock, but if we were dropping the default due to a cascaded delete of some function it depended on, maybe not.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> o -Add ALTER TABLE DROP COLUMN feature
-
由 Bruce Momjian 提交于
> o -Add ALTER TABLE DROP COLUMN feature [drop]
-
由 Tom Lane 提交于
code review by Tom Lane. Remaining issues: functions that take or return tuple types are likely to break if one drops (or adds!) a column in the table defining the type. Need to think about what to do here. Along the way: some code review for recent COPY changes; mark system columns attnotnull = true where appropriate, per discussion a month ago.
-
- 01 8月, 2002 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Hiroshi Inoue 提交于
whose first non-space character is '('. 2) Handle Insert .. () VALUES ().
-
由 Tom Lane 提交于
attstattarget to indicate 'use the default'. The default is now a GUC variable default_statistics_target, and so may be changed on the fly. Along the way we gain the ability to have pg_dump dump the per-column statistics target when it's not the default. Patch by Neil Conway, with some kibitzing from Tom Lane.
-
- 31 7月, 2002 14 次提交
-
-
由 Bruce Momjian 提交于
> * -Remove LockMethodTable.prio field, not used (Bruce)
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> * -Add getpid() function to backend
-
由 Tom Lane 提交于
this only works against 7.3 or later databases; the pushups required to do it without regprocedure/regtype/etc seem more trouble than they're worth, considering that existing users aren't expecting pg_dump support for this.
-
由 Bruce Momjian 提交于
< o ALTER TABLE ADD COLUMN column SET DEFAULT should fill existing > o ALTER TABLE ADD COLUMN column DEFAULT should fill existing
-
由 Bruce Momjian 提交于
< o ALTER TABLE ALTER COLUMN column SET DEFAULT should fill existing > o ALTER TABLE ADD COLUMN column SET DEFAULT should fill existing
-
由 Bruce Momjian 提交于
All of the internal tags are of the latter. The other thing I noticed is that most of the quick examples in the file use a para and synopsis. Is there a reason we're not using <example/> ? Rod Taylor
-
由 Bruce Momjian 提交于
> * Use CHECK constraints to improve optimizer decisions
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
OPERATOR CLASS commands.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-