- 26 6月, 2003 13 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> * Allow the identifier length to be increased via a configure option
-
由 Bruce Momjian 提交于
> * Promote debug_query_string into a server-side function current_query()
-
由 Bruce Momjian 提交于
not ready yet.
-
由 Bruce Momjian 提交于
Joe Conway
-
由 Tom Lane 提交于
HH:MM:SS.SSS... when there is a nonzero part-of-a-day field in an interval value. The seconds part used to be suppressed if zero, but there's no equivalent behavior for timestamp, and since we're modeling this format on timestamp it's probably wrong. Per complaint and patch from Larry Rosenman.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
This is no longer necessary or appropriate since we don't use zero typeid as a wildcard anymore, and it fixes a nasty performance problem with functions with many parameters. Per recent example from Reuven Lerner.
-
由 Tom Lane 提交于
-
由 Michael Meskes 提交于
-
由 Michael Meskes 提交于
-
- 25 6月, 2003 27 次提交
-
-
由 Bruce Momjian 提交于
-
由 Michael Meskes 提交于
-
由 Michael Meskes 提交于
-
由 Bruce Momjian 提交于
The attached fixes select_common_type() to support the below case: create table t1( c1 int); create domain dom_c1 int; create table t2(c1 dom_c1); select * from t1 join t2 using( c1 ); I didn't see a need for maintaining the domain as the preferred type. A simple getBaseType() call on all elements of the list seems to be enough. -- Rod Taylor <rbt@rbt.ca>
-
由 Bruce Momjian 提交于
> * -Allow CIDR format to be used in pg_hba.conf
-
由 Bruce Momjian 提交于
> * -Allow UPDATE to use SET col = DEFAULT
-
由 Bruce Momjian 提交于
Rod Taylor
-
由 Bruce Momjian 提交于
after the CHECK. Cluster depends on the index name, so I thought it wise to ensure all names are available, rather than leaving off the CONSTRAINT "$n" portion for internally named constraints. CREATE TABLE jkey (col integer primary key); CREATE TABLE j (col integer REFERENCES jkey); ALTER TABLE j ADD CHECK(col > 5); This is a problem in 7.3 series as well as -Tip. Rod Taylor <rbt@rbt.ca>
-
由 Bruce Momjian 提交于
pg_get_constraintdef() for >= 70400. Rod Taylor <rbt@rbt.ca>
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
- LIKE <subtable> [ INCLUDING DEFAULTS | EXCLUDING DEFAULTS ] - Quick cleanup of analyze.c function prototypes. - New non-reserved keywords (INCLUDING, EXCLUDING, DEFAULTS), SQL 200X Opted not to extend for check constraints at this time. As per the definition that it's user defined columns, OIDs are NOT inherited. Doc and Source patches attached. -- Rod Taylor <rbt@rbt.ca>
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> * Allow creation of a libpq-only tarball >
-
由 Bruce Momjian 提交于
incompatible. I believe the attached xref meets the intent of the perform.sgml change. -- Rod Taylor <rbt@rbt.ca>
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Andrew Dunstan
-
由 Bruce Momjian 提交于
> http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/include/libpq/pqcomm.h.diff?r1=1.85&r2=1.86 > > modified SockAddr, but no corresponding change was made here > (fe-auth.c:612): > > case AUTH_REQ_KRB5: > #ifdef KRB5 > if (pg_krb5_sendauth(PQerrormsg, conn->sock, &conn->laddr.in, > &conn->raddr.in, > hostname) != STATUS_OK) > > It's not obvious to me what the change ought to be though. This patch should hopefully fix both kerberos 4 and 5. Kurt Roeckx
-
由 Bruce Momjian 提交于
> rexec and making it an untrusted language. Last time I looked, it didn't > look particularly difficult. I've set aside some time next week, so stay > tuned. Attached is a patch that removes all of the RExec code from plpython from the current PostgreSQL CVS. In addition, plpython needs to be changed to an untrusted language in createlang. Please let me know if there are any problems. Kevin Jacobs
-
由 Bruce Momjian 提交于
slave servers. I haven't tested it very well, so use at your own risk (and I recommend against using it in production). Basically, I have a central database server that has 4 summary tables inside it replicated to a remote slave (these database tables are for my mail server authentication, so these are replicated to another server tuned for many connections, and so I don't have postgres connections opened straight to my back-end database server). Unfortunately, I also wanted to implement a replication database server for hot-backups. I realized, too late, that the replication process is pretty greedy and will try to replicate all tables marked as a "MasterAddTable". To make a long story, I made a patch to RServ.pm and Replicate that allows you to specify, on the command line, a list of tables that you want to replicate...it'll ignore all others. I haven't finished, since this has to be integrated with CleanLog for instance, but this should (and does) suffice for the moment. I have yet to test it with two slaves, but at least my mail server replication database now works (it was failing every time it tried to replicate, for a variety of reasons). Anyone have any suggestions on how to improve on this? (or, if someone more familiar with this code wants to take the ball and run with it, you're welcome to). -- Michael A Nachbaur <mike@nachbaur.com>
-
由 Bruce Momjian 提交于
addresses. Andrew Dunstan
-
由 Bruce Momjian 提交于
chapter. I got tired of hitting the 'up' link, then finding the table in the table of contents, and following it back down. Rod Taylor
-
由 Bruce Momjian 提交于
Josh Berkus
-
由 Bruce Momjian 提交于
Runtime.sgml and dependant files. Josh Berkus
-
由 Bruce Momjian 提交于
- Don't attempt to convert partial or expressional unique indexes - Don't attempt to convert unique indexes based on a non-default opclasses - Untested prevention of conversion of non-btree indexes unique indexes. Untested as postgresql doesn't allow hash, gist, or rtree based indexes to be unique. rbt=# create unique index t on a using hash (col); ERROR: DefineIndex: access method "hash" does not support UNIQUE indexes rbt=# create unique index t on a using gist (col); ERROR: DefineIndex: access method "gist" does not support UNIQUE indexes rbt=# select version(); version ------------------------------------------------------------------------ PostgreSQL 7.4devel on i386-unknown-freebsd4.8, compiled by GCC 2.95.4 Rod Taylor
-
由 Bruce Momjian 提交于
connections to dblink. Shridhar Daithanka
-
由 Bruce Momjian 提交于
This is a bug in python interface module, postgresql-7.3.3/src/interfaces/python/pg.py. _quote() function fails due to integer overflow if input d is larger than max integer. In the case where the column type is "BIGINT", the input d may very well be larger than max integer while its type, t, is labeled 'int'. The conversion on line 19, return "%d" % int(d), will fail due to "OverflowError: long int too large to convert to int". Please describe a way to repeat the problem. Please try to provide a concise reproducible example, if at all possible: ---------------------------------------------------------------------- [1] create a table with a column type 'BIGINT'. [2] use pg.DB.insert() to insert a value that is larger than max integer If you know how this problem might be fixed, list the solution below: --------------------------------------------------------------------- Just changing the conversion at line 19 of pg.py to long(d) instead of int(d) should fix it. The following is a patch: Chih-Hao Huang
-