- 03 7月, 2008 5 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Joe Conway 提交于
pains to pass the ERROR message components locally, including using the passed SQLSTATE. Also wrap the passed info in an appropriate CONTEXT message. Addresses complaint by Henry Combrinck. Joe Conway, with much good advice from Tom Lane.
-
由 Tom Lane 提交于
Guillaume Lelarge, with some additional fixes by me.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
fix by Kris Jurka.
-
- 02 7月, 2008 4 次提交
-
-
由 Bruce Momjian 提交于
which are available if LOCK_DEBUG is defined.
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
* Add database and transaction-level triggers
-
由 Bruce Momjian 提交于
> * Fix TRUNCATE ... RESTART IDENTITY so its affect on sequences is rolled > back on transaction abort
-
- 01 7月, 2008 11 次提交
-
-
由 Heikki Linnakangas 提交于
output for CREATE FUNCTION. This makes it easier to read especially if the function body is long. Original idea and patch by Greg Sabino Mullane, though this is a stripped down version of that.
-
由 Heikki Linnakangas 提交于
of different types than the underlying column. The capability isn't yet used for anything, but will be required by upcoming patch to analyze tsvector columns. Jan Urbanski
-
由 Magnus Hagander 提交于
-
由 Magnus Hagander 提交于
one for client-side, restoring the previous behaviour with different sort order for the 'log' level. Also, remove redundant list of available options, since the enum code will output it automatically.
-
由 Tom Lane 提交于
timezone setting in the current year and for 100 years back, rather than always examining years 1904-2004. The original coding would have problems distinguishing zones whose behavior diverged only after 2004; which is a situation we will surely face sometime, if it's not out there already. In passing, also prevent selection of the dummy "Factory" timezone, even if that's exactly what the system is using. Reporting time as GMT seems better than that.
-
由 Tom Lane 提交于
backend. If so, send a LOG message to the postmaster log, and if the table is beyond the vacuum-for-wraparound horizon, forcibly drop it. Per recent discussions. Perhaps we ought to back-patch this, but it probably needs to age a bit in HEAD first.
-
由 Bruce Momjian 提交于
observation by David Fetter.
-
由 Bruce Momjian 提交于
values as postgresql.conf.
-
由 Bruce Momjian 提交于
> o Add "auto" expanded mode that outputs in expanded format if > "wrapped" mode can't wrap the output to the screen width > > http://archives.postgresql.org/pgsql-hackers/2008-05/msg00417.php >
-
由 Bruce Momjian 提交于
> o Add option to wrap column values at whitespace boundaries, > rather than chopping them at a fixed width. > Currently, "wrapped" format chops values into fixed > widths. Perhaps the word wrapping could use the same > algorithm documented in the W3C specification. > http://archives.postgresql.org/pgsql-hackers/2008-05/msg00404.php > http://www.w3.org/TR/CSS21/tables.html#auto-table-layout
-
由 Teodor Sigaev 提交于
laser <laserlist@pgsqldb.com> with some editorization by me.
-
- 30 6月, 2008 2 次提交
-
-
由 Heikki Linnakangas 提交于
As the buffer could now be a lot larger than before, and copying it could thus be a lot more expensive than before, use strcpy instead of memcpy to copy the query string, as was already suggested in comments. Also, only copy the PgBackendStatus struct and string if the slot is in use. Patch by Thomas Lee, with some changes by me.
-
由 Tom Lane 提交于
space is tracked via GetMemoryChunkSpace, there's really no advantage to duplicating datumCopy's innards here. This is one bit of my toast indirection patch that should go in anyway.
-
- 29 6月, 2008 1 次提交
-
-
由 Tom Lane 提交于
it ought to conform to the rest of palloc.h in using Size for sizes.
-
- 28 6月, 2008 2 次提交
-
-
由 Tom Lane 提交于
of any lower outer join, even if it also references the non-nullable side and so could not get pushed below the outer join anyway. We need this in case the clause is an OR clause: if it doesn't get marked outerjoin_delayed, create_or_index_quals() could pull an indexable restriction for the nullable side out of it, leading to wrong results as demonstrated by today's bug report from toruvinn. (See added regression test case for an example.) In principle this has been wrong for quite a while. In practice I don't think any branch before 8.3 can really show the failure, because create_or_index_quals() will only pull out indexable conditions, and before 8.3 those were always strict. So though we might have improperly generated null-extended rows in the outer join, they'd get discarded from the result anyway. The gating factor that makes the failure visible is that 8.3 considers "col IS NULL" to be indexable. Hence I'm not going to risk back-patching further than 8.3.
-
由 Magnus Hagander 提交于
Hiroshi Saito
-
- 27 6月, 2008 9 次提交
-
-
由 Tom Lane 提交于
taking the maximum of any child rel's width, we should weight the widths proportionally to the number of rows expected from each child. In hindsight this is obviously correct because row width is really a proxy for the total physical size of the relation. Per discussion with Scott Carey (bug #4264).
-
由 Bruce Momjian 提交于
values to libpq.
-
由 Bruce Momjian 提交于
> > * Fix system views like pg_stat_all_tables to use set-returning > functions, rather than views of per-column functions
-
由 Tom Lane 提交于
truly distinct version of IF. Per suggestion from Marko Kreen.
-
由 Tom Lane 提交于
vintage Linux is even more broken than we realized: a link to libreadline will succeed, and fail only at runtime. It seems that an AC_TRY_RUN test is the only reliable way to check whether this is really safe. Per report from Tatsuo.
-
由 Bruce Momjian 提交于
appear in a paragraph. Andy Anderson
-
由 Bruce Momjian 提交于
wasn't working.
-
由 Teodor Sigaev 提交于
and non-C locale. Fix is just to use correct source's length for char2wchar call.
-
- 26 6月, 2008 6 次提交
-
-
由 Michael Meskes 提交于
-
由 Bruce Momjian 提交于
* Improve server security options http://archives.postgresql.org/pgsql-hackers/2008-04/msg01875.php http://archives.postgresql.org/pgsql-hackers/2008-05/msg00000.php
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
postmaster.opts.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> > * Improve LDAP authentication configuration options > > http://archives.postgresql.org/pgsql-hackers/2008-04/msg01745.php
-