OSDN Git Service
Peter Eisentraut [Sat, 13 Jun 2009 13:43:34 +0000 (13:43 +0000)]
Tweak the display of incoming foreign-key constraints in \d, per discussion
on hackers. Also, take that string out of the translation roster, since
it's now entirely pseudo-SQL.
Tom Lane [Fri, 12 Jun 2009 19:48:53 +0000 (19:48 +0000)]
Improve documentation about GiST opclass support functions.
Dimitri Fontaine
Tom Lane [Fri, 12 Jun 2009 16:17:29 +0000 (16:17 +0000)]
Fix several places where a function was declared static and then defined
without static. Per testing with a compiler that complains about this.
Tom Lane [Fri, 12 Jun 2009 15:53:32 +0000 (15:53 +0000)]
Add info about minimum recommended AIX fix levels, per Laurenz Albe.
Marc G. Fournier [Fri, 12 Jun 2009 05:19:22 +0000 (05:19 +0000)]
time to tag rc1 ...
Bruce Momjian [Fri, 12 Jun 2009 03:09:07 +0000 (03:09 +0000)]
Tighten typedef check for Linux.
Bruce Momjian [Fri, 12 Jun 2009 03:04:48 +0000 (03:04 +0000)]
Mention BSD/OS find_typedef behavior.
Bruce Momjian [Thu, 11 Jun 2009 22:21:44 +0000 (22:21 +0000)]
Document struct/union problem with pgindent.
Tom Lane [Thu, 11 Jun 2009 21:44:26 +0000 (21:44 +0000)]
Update release notes to today.
Tom Lane [Thu, 11 Jun 2009 20:46:11 +0000 (20:46 +0000)]
Revisit AlterTableCreateToastTable's API once again, hoping to make it what
pg_migrator actually needs and not just a partial solution. We have to be
able to specify the OID that the new toast table should be created with.
Tom Lane [Thu, 11 Jun 2009 19:00:15 +0000 (19:00 +0000)]
Remove our inadequate kluge that tried to get AIX's various broken versions
of getaddrinfo() to work. Instead, recommend updating the OS to get a working
version of getaddrinfo. Per recent discussions.
Tom Lane [Thu, 11 Jun 2009 18:30:03 +0000 (18:30 +0000)]
Mark contrib's GiST and GIN opclass support functions as STRICT, for safety.
(Note: GiST penalty functions could possibly be non-strict, but none are at
present.)
Tom Lane [Thu, 11 Jun 2009 17:45:38 +0000 (17:45 +0000)]
Update time zone data files to tzdata release 2009i: DST law changes in
Bangladesh, Egypt, Jordan, Pakistan.
Tom Lane [Thu, 11 Jun 2009 17:25:39 +0000 (17:25 +0000)]
Fix things so that you can still do "select foo()" where foo is a SQL
function returning setof record. This used to work, more or less
accidentally, but I had broken it while extending the code to allow
materialize-mode functions to be called in select lists. Add a regression
test case so it doesn't get broken again. Per gripe from Greg Davidson.
Tom Lane [Thu, 11 Jun 2009 16:14:18 +0000 (16:14 +0000)]
Somebody seems to have thought they could get away without checking for
rsinfo->expectedDesc == NULL in deflist_to_tuplestore(), but that doesn't
look very safe to me. Noted in passing while studying problem report
from Greg Davidson.
Bruce Momjian [Thu, 11 Jun 2009 14:49:15 +0000 (14:49 +0000)]
8.4 pgindent run, with new combined Linux/FreeBSD/MinGW typedef list
provided by Andrew.
Bruce Momjian [Thu, 11 Jun 2009 03:14:08 +0000 (03:14 +0000)]
Add FreeBSD support for find_typedef, per request from Andrew.
Peter Eisentraut [Wed, 10 Jun 2009 23:42:44 +0000 (23:42 +0000)]
Translation updates
Peter Eisentraut [Wed, 10 Jun 2009 23:11:52 +0000 (23:11 +0000)]
Arrange that the string "syntax error" generated by bison is translated.
Tom Lane [Wed, 10 Jun 2009 23:03:32 +0000 (23:03 +0000)]
Fix ill-advised whitespace prettification, per buildfarm.
Peter Eisentraut [Wed, 10 Jun 2009 22:34:11 +0000 (22:34 +0000)]
Clarify to the translator that plpgsql_yyerror() deals with the translation
of "syntax error", not the literal string.
This same change was made in the backend a while ago; but it applies to
plpgsql as well.
Tom Lane [Wed, 10 Jun 2009 22:12:28 +0000 (22:12 +0000)]
Properly mark pg_freespace() function as strict. Also update
uninstall script to match reality.
Peter Eisentraut [Wed, 10 Jun 2009 21:51:56 +0000 (21:51 +0000)]
Clarify error message
Tom Lane [Wed, 10 Jun 2009 21:24:11 +0000 (21:24 +0000)]
Support Kerberos on platforms where libcom_err depends on OpenSSL, as
reportedly is true on OpenBSD. Also support OpenBSD's spelling of
-Wl,--as-needed. Per Simon Bertrang.
Tom Lane [Wed, 10 Jun 2009 20:25:41 +0000 (20:25 +0000)]
Add warning that xpath() doesn't work with non-UTF8 data.
Peter Eisentraut [Wed, 10 Jun 2009 20:02:15 +0000 (20:02 +0000)]
Improve capitalization and punctuation in recently added GiST message.
Tom Lane [Wed, 10 Jun 2009 19:21:37 +0000 (19:21 +0000)]
Add a warning about possible strange behavior of volatile functions
in cursors. This has always been the case, but given the lack of user
complaints about it, I'm not going to bother back-patching this.
Tom Lane [Wed, 10 Jun 2009 18:54:16 +0000 (18:54 +0000)]
Keep rs_startblock the same during heap_rescan, so that a rescan of a SeqScan
node starts from the same place as the first scan did. This avoids surprising
behavior of scrollable and WITH HOLD cursors, as seen in Mark Kirkwood's bug
report of yesterday.
It's not entirely clear whether a rescan should be forced to drop out of the
syncscan mode, but for the moment I left the code behaving the same on that
point. Any change there would only be a performance and not a correctness
issue, anyway.
Back-patch to 8.3, since the unstable behavior was created by the syncscan
patch.
Tom Lane [Wed, 10 Jun 2009 16:31:32 +0000 (16:31 +0000)]
Fix cash_in() to behave properly in locales where frac_digits is zero,
eg Japan. Report and fix by Itagaki Takahiro. Also fix CASHDEBUG printout
format for branches with 64-bit money type, and some minor comment cleanup.
Back-patch to 7.4, because it's broken all the way back.
Bruce Momjian [Wed, 10 Jun 2009 15:13:45 +0000 (15:13 +0000)]
Fix Linux typedef code.
Peter Eisentraut [Wed, 10 Jun 2009 07:03:34 +0000 (07:03 +0000)]
Correct/improve the datetime_precision field in the information schema.
In particular, always show 0 for the date type instead of null, and show
6 (the default) for time, timestamp, and interval without a declared
precision. This is now in fuller conformance with the SQL standard.
Also clarify the documentation about this.
discovered and analyzed by Konstantin Izmailov and Tom Lane
Tom Lane [Wed, 10 Jun 2009 05:05:03 +0000 (05:05 +0000)]
Make handling of INTERVAL DAY TO MINUTE and INTERVAL DAY TO SECOND input
more consistent with other cases, by having an unlabeled integer field
be treated as a number of minutes or seconds respectively. These cases
are outside the spec (which insists on full "dd hh:mm" or "dd hh:mm:ss"
input respectively), so it's not much help to us in deciding what to do.
But with this change, it's uniformly the case that an unlabeled integer
will be considered as being a number of the interval's rightmost field.
The change also takes us back to the 8.3 behavior of throwing error
for certain ambiguous inputs such as INTERVAL '1 2' DAY TO MINUTE.
Per recent discussion.
Tom Lane [Wed, 10 Jun 2009 03:44:35 +0000 (03:44 +0000)]
Ensure xmlFree(NULL) is a no-op instead of a core dump. Per report from
Sergey Burladyan, there are at least some dank corners of libxml2 that
assume this behavior, even though their published documentation suggests
they shouldn't.
This is only really a live problem in 8.3, but the code is still there
for possible debugging use in HEAD, so patch both branches.
Bruce Momjian [Wed, 10 Jun 2009 03:38:32 +0000 (03:38 +0000)]
Fix BSD find_typedef logic.
Bruce Momjian [Wed, 10 Jun 2009 01:51:44 +0000 (01:51 +0000)]
Update pgindent instructions.
Bruce Momjian [Wed, 10 Jun 2009 01:47:59 +0000 (01:47 +0000)]
Document new location for typedef list.
Peter Eisentraut [Tue, 9 Jun 2009 22:00:57 +0000 (22:00 +0000)]
Fix xmlattribute escaping XML special characters twice (bug #4822).
Author: Itagaki Takahiro <itagaki.takahiro@oss.ntt.co.jp>
Tom Lane [Tue, 9 Jun 2009 19:51:00 +0000 (19:51 +0000)]
Mark internal_in as not strict, so that the construct "null::internal"
will throw an error, rather than possibly allowing someone to synthesize
a manual call to an internal-accepting function. As of CVS HEAD and existing
releases, all such functions are either STRICT or careful about null inputs,
so there is no current security issue here. But it seems like a good idea
to lock this down to protect against future mistakes.
In passing, similarly lock down trigger_in, language_handler_in, opaque_in,
and shell_in. These are not believed to present any security risk, but
there's still no good reason to allow nulls of these types to be created.
I left the polymorphic pseudotypes (anyelement etc) alone, since a null
of one of those types doesn't seem to be a problem --- the worst you can
say about it is that it doesn't have an underlying non-polymorphic type.
If we were to make this change during normal development, we'd just
automatically bump catversion for a pg_proc.h change. But since this doesn't
create a compatibility risk and isn't believed to be fixing a live bug, it
seems better not to force a catversion bump in late beta.
Alvaro Herrera [Tue, 9 Jun 2009 19:36:28 +0000 (19:36 +0000)]
Fix typo, per Tom
Tom Lane [Tue, 9 Jun 2009 18:15:04 +0000 (18:15 +0000)]
Switch order of tests to avoid possible Assert failure for
"array_agg_finalfn(null)". We should modify pg_proc entries to prevent this
query from being accepted, but let's just make the function itself secure too.
Per my note of today.
Tom Lane [Tue, 9 Jun 2009 17:41:02 +0000 (17:41 +0000)]
Restore dblink_current_query() to being a C-language function, so as to not
create an ABI break between 8.3 and 8.4. It is still just a wrapper around
the built-in current_query() function, but at a different implementation
level. Per my proposal.
Note: this change doesn't break 8.4beta installations, since their
SQL-language definition of the function still works fine.
Alvaro Herrera [Tue, 9 Jun 2009 16:41:02 +0000 (16:41 +0000)]
Dynamically set a lower bound on autovacuum nap time so that we don't rebuild
the database list too often.
Per bug report from Łukasz Jagiełło and ensuing discussion on
pgsql-performance.
Joe Conway [Tue, 9 Jun 2009 16:35:36 +0000 (16:35 +0000)]
Default client encoding to server encoding for dblink connections. Addresses
issue raised by Ruzsinszky Attila and confirmed by others.
----------------------------------------------------------------------
Tom Lane [Tue, 9 Jun 2009 14:36:06 +0000 (14:36 +0000)]
Fix failure to double-quote function argument names when needed, in
pg_get_function_arguments() and related functions. Per report from
Andreas Nolte.
Peter Eisentraut [Mon, 8 Jun 2009 21:32:33 +0000 (21:32 +0000)]
Fix map_sql_table_to_xmlschema() with dropped attributes.
also backpatched to 8.3
Tom Lane [Mon, 8 Jun 2009 16:22:44 +0000 (16:22 +0000)]
Fix contrib/pageinspect to not create an ABI breakage between 8.3 and 8.4.
The original implementation of the 3-argument form of get_raw_page() risked
core dumps if the 8.3 SQL function definition was mistakenly used with the
8.4 module, which is entirely likely after a dump-and-reload upgrade. To
protect 8.4 beta testers against upgrade problems, add a check on PG_NARGS.
In passing, fix missed additions to the uninstall script, and polish the
docs a trifle.
Tom Lane [Mon, 8 Jun 2009 14:57:21 +0000 (14:57 +0000)]
Be a bit more verbose about the effects of string literal processing
changes in plpgsql. Per bug #4843.
Tom Lane [Sun, 7 Jun 2009 20:09:34 +0000 (20:09 +0000)]
Revert my patch of 2009-04-04 that removed contrib/intarray's definitions of
the <@ and @> operators. These are not in fact equivalent to the built-in
anyarray operators of the same names, because they have different behavior for
empty arrays, namely they don't think empty arrays are contained in anything.
That is mathematically wrong, no doubt, but until we can persuade GIN indexes
to implement the mathematical definition we should probably not change this.
Another reason for not changing it now is that we can't yet ensure the
opclasses will be updated correctly in a dump-and-reload upgrade. Per
recent discussions.
Tom Lane [Sat, 6 Jun 2009 22:13:52 +0000 (22:13 +0000)]
Improve the IndexVacuumInfo/IndexBulkDeleteResult API to allow somewhat sane
behavior in cases where we don't know the heap tuple count accurately; in
particular partial vacuum, but this also makes the API a bit more useful
for ANALYZE. This patch adds "estimated_count" flags to both structs so
that an approximate count can be flagged as such, and adjusts the logic
so that approximate counts are not used for updating pg_class.reltuples.
This fixes my previous complaint that VACUUM was putting ridiculous values
into pg_class.reltuples for indexes. The actual impact of that bug is
limited, because the planner only pays attention to reltuples for an index
if the index is partial; which probably explains why beta testers hadn't
noticed a degradation in plan quality from it. But it needs to be fixed.
The whole thing is a bit messy and should be redesigned in future, because
reltuples now has the potential to drift quite far away from reality when
a long period elapses with no non-partial vacuums. But this is as good as
it's going to get for 8.4.
Joe Conway [Sat, 6 Jun 2009 21:27:56 +0000 (21:27 +0000)]
Add support for using SQL/MED compliant FOREIGN DATA WRAPPER, SERVER,
and USER MAPPING as method to supply dblink connect parameters. Per
mailing list and PGCon discussions.
Tom Lane [Sat, 6 Jun 2009 03:45:36 +0000 (03:45 +0000)]
Move variable declaration to avoid 'unused variable' warning when the
ifdef doesn't trigger. Not worth back-patching. Per buildfarm reports.
Tom Lane [Sat, 6 Jun 2009 02:39:40 +0000 (02:39 +0000)]
Fix a serious bug introduced into GIN in 8.4: now that MergeItemPointers()
is supposed to remove duplicate heap TIDs, we have to be sure to reduce the
tuple size and posting-item count accordingly in addItemPointersToTuple().
Failing to do so resulted in the effective injection of garbage TIDs into the
index contents, ie, whatever happened to be in the memory palloc'd for the
new tuple. I'm not sure that this fully explains the index corruption
reported by Tatsuo Ishii, but the test case I'm using no longer fails.
Andrew Dunstan [Fri, 5 Jun 2009 20:32:00 +0000 (20:32 +0000)]
Adjust recent PERL_SYS_INIT3 call to avoid platforms where it might fail, and to remove compilation warning. Backpatch the release 7.4
Tom Lane [Fri, 5 Jun 2009 18:50:47 +0000 (18:50 +0000)]
GIN's ItemPointerIsMin, ItemPointerIsMax, and ItemPointerIsLossyPage macros
should use GinItemPointerGetBlockNumber/GinItemPointerGetOffsetNumber,
not ItemPointerGetBlockNumber/ItemPointerGetOffsetNumber, because the latter
will Assert() on ip_posid == 0, ie a "Min" pointer. (Thus, ItemPointerIsMin
has never worked at all, but it seems unused at present.) I'm not certain
that the case can occur in normal functioning, but it's blowing up on me
while investigating Tatsuo-san's data corruption problem. In any case it
seems like a problem waiting to bite someone.
Back-patch just in case this really is a problem for somebody in the field.
Andrew Dunstan [Fri, 5 Jun 2009 18:29:56 +0000 (18:29 +0000)]
Search for versioned perl library instead of using hardcoded name on Windows. Backpatch to release 8.3
Bruce Momjian [Fri, 5 Jun 2009 13:40:31 +0000 (13:40 +0000)]
Remove sleep() from backup script example; not needed anymore.
Fujii Masao
Tom Lane [Thu, 4 Jun 2009 19:17:39 +0000 (19:17 +0000)]
Trivial code style cleanup around a couple of ngettext calls.
Tom Lane [Thu, 4 Jun 2009 19:16:48 +0000 (19:16 +0000)]
Remove a couple of debugging messages that have been #ifdef'd out for ages.
Seems silly to ask translators to expend work on these, especially in
pluralized variants.
Tom Lane [Thu, 4 Jun 2009 18:33:08 +0000 (18:33 +0000)]
Improve the recently-added support for properly pluralized error messages
by extending the ereport() API to cater for pluralization directly. This
is better than the original method of calling ngettext outside the elog.c
code because (1) it avoids double translation, which wastes cycles and in
the worst case could give a wrong result; and (2) it avoids having to use
a different coding method in PL code than in the core backend. The
client-side uses of ngettext are not touched since neither of these concerns
is very pressing in the client environment. Per my proposal of yesterday.
Andrew Dunstan [Thu, 4 Jun 2009 15:59:55 +0000 (15:59 +0000)]
Initialise perl library as documented in perl API. Backpatch to release 7.4.
Bruce Momjian [Wed, 3 Jun 2009 20:34:29 +0000 (20:34 +0000)]
Wording improvement for recent sesssion identifier SQL query.
Tom Lane [Wed, 3 Jun 2009 20:24:51 +0000 (20:24 +0000)]
Clean up ecpg's use of mmerror(): const-ify the format argument, add an
__attribute__() marker so that gcc can validate the format string against
the actual arguments, get rid of overcomplicated and unsafe usage in
base_yyerror().
Tom Lane [Wed, 3 Jun 2009 18:42:13 +0000 (18:42 +0000)]
Fix tsquerysel() to not fail on an empty TSQuery. Per report from
Tatsuo Ishii.
Tom Lane [Wed, 3 Jun 2009 16:17:49 +0000 (16:17 +0000)]
Change rather bizarre code ordering in get_id(). This isn't strictly
cosmetic --- I'm wondering if geteuid could have side effects on errno,
thus possibly resulting in a misleading error message after failure of
getpwuid.
Tom Lane [Wed, 3 Jun 2009 15:06:48 +0000 (15:06 +0000)]
Improve comment about 'if (1)' hack in copy.c macros.
Bruce Momjian [Wed, 3 Jun 2009 14:48:33 +0000 (14:48 +0000)]
Add comment about why "((void) 0)" is used in copy macros.
Bruce Momjian [Wed, 3 Jun 2009 00:38:34 +0000 (00:38 +0000)]
Add example of how to generate the session identifier from pg_stat_activity.
Tom Lane [Tue, 2 Jun 2009 17:37:55 +0000 (17:37 +0000)]
Remove the old advice to keep from_collapse_limit less than geqo_threshold,
instead just pointing out that a larger value may trigger use of GEQO.
Per Robert Haas.
In passing, do a bit of wordsmithing on the Genetic Query Optimizer section.
Heikki Linnakangas [Tue, 2 Jun 2009 06:18:06 +0000 (06:18 +0000)]
Only recycle normal files in pg_xlog as WAL segments. pg_standby creates
symbolic links with the -l option, and as Fujii Masao pointed out we ended up
overwriting files in the archive directory before this patch. Patch by
Aidan Van Dyk, Fujii Masao and me.
Backpatch to 8.3, where pg_standby was introduced.
Joe Conway [Tue, 2 Jun 2009 03:21:56 +0000 (03:21 +0000)]
Fix dblink_get_result() as reported by Oleksiy Shchukin. Refactor a bit
while we're at it per request by Tom Lane. Specifically, don't try to
perform dblink_send_query() via dblink_record_internal() -- it was
inappropriate and ugly.
Tom Lane [Mon, 1 Jun 2009 23:55:15 +0000 (23:55 +0000)]
Change AdjustIntervalForTypmod to not discard higher-order field values on the
grounds that they don't fit into the specified interval qualifier (typmod).
This behavior, while of long standing, is clearly wrong per spec --- for
example the value INTERVAL '999' SECOND means 999 seconds and should not be
reduced to less than 60 seconds.
In some cases there could be grounds to raise an error if higher-order field
values are not given as zero; for example '1 year 1 month'::INTERVAL MONTH
should arguably be taken as an error rather than equivalent to 13 months.
However our internal representation doesn't allow us to do that in a fashion
that would consistently reject all and only the cases that a strict reading
of the spec would suggest. Also, seeing that for example INTERVAL '13' MONTH
will print out as '1 year 1 mon', we have to be careful not to create a
situation where valid data will fail to dump and reload. The present patch
therefore takes the attitude of not throwing an error in any such case.
We might want to revisit that in future but it would take more redesign
than seems prudent in late beta.
Per a complaint from Sebastien Flaesch and subsequent discussion. While
at other times we might have just postponed such an issue to the next
development cycle, 8.4 already has changed the parsing of interval literals
quite a bit in an effort to accept all spec-compliant cases correctly.
This seems like a change that should be part of that rather than coming
along later.
Tom Lane [Mon, 1 Jun 2009 16:55:11 +0000 (16:55 +0000)]
Fix DecodeInterval to report an error for multiple occurrences of DAY, WEEK,
YEAR, DECADE, CENTURY, or MILLENIUM fields, just as it always has done for
other types of fields. The previous behavior seems to have been a hack to
avoid defining bit-positions for all these field types in DTK_M() masks,
rather than something that was really considered to be desired behavior.
But there is room in the masks for these, and we really need to tighten up
at least the behavior of DAY and YEAR fields to avoid unexpected behavior
associated with the 8.4 changes to interpret ambiguous fields based on the
interval qualifier (typmod) value. Per my example and proposed patch.
Tom Lane [Sun, 31 May 2009 20:55:37 +0000 (20:55 +0000)]
Update obsolete comment in index_drop(). When the comment was written,
queries frequently took no lock at all on individual indexes. That's not
true any more, but we still need lock on the parent table to make it safe
to use cached lists of index OIDs.
Michael Meskes [Fri, 29 May 2009 13:54:52 +0000 (13:54 +0000)]
Change macros to make gcc quiet when parsing.
Bruce Momjian [Thu, 28 May 2009 20:02:10 +0000 (20:02 +0000)]
Document that forking while having open libpq connections is not
advised.
Heikki Linnakangas [Thu, 28 May 2009 11:02:16 +0000 (11:02 +0000)]
When archiving is enabled, rotate the last WAL segment at shutdown so that
all transactions are archived.
Original patch by Guillaume Smet.
Tom Lane [Wed, 27 May 2009 22:12:53 +0000 (22:12 +0000)]
Improve release note explanation of the change in libpq's handling of
default usernames versus Kerberos tickets. Per confusion about what
bug #4824 was really about.
Magnus Hagander [Wed, 27 May 2009 21:08:22 +0000 (21:08 +0000)]
Properly return the usermap result when doing gssapi authentication. Without
this, the username was in practice never matched against the kerberos principal
used to log in.
Peter Eisentraut [Wed, 27 May 2009 20:47:55 +0000 (20:47 +0000)]
Fix to use the same format specifiers in both branches of a ngettext().
Zdenek Kotala
Tom Lane [Wed, 27 May 2009 20:42:29 +0000 (20:42 +0000)]
Ignore RECHECK in CREATE OPERATOR CLASS, just throwing a NOTICE, instead of
throwing an error as 8.4 had been doing. The error interfered with porting
old database definitions (particularly for pg_migrator) without really buying
any safety. Per bug #4817 and subsequent discussion.
Peter Eisentraut [Wed, 27 May 2009 19:41:58 +0000 (19:41 +0000)]
Fix compiler warnings on Sun Studio of the sort
"tsquery_op.c", line 193: warning: syntax error: empty declaration
Zdenek Kotala
Michael Meskes [Wed, 27 May 2009 14:16:51 +0000 (14:16 +0000)]
Reverting patch just in case a compiler treats this enum as signed.
Bruce Momjian [Wed, 27 May 2009 12:28:55 +0000 (12:28 +0000)]
Remove tabs from SGML file.
Tom Lane [Wed, 27 May 2009 01:18:06 +0000 (01:18 +0000)]
Improve documentation about function volatility: mention the snapshot
visibility effects in a couple of places where people are likely to look
for it. Per discussion of recent question from Karl Nack.
Tom Lane [Tue, 26 May 2009 17:36:05 +0000 (17:36 +0000)]
Allow the second argument of pg_get_expr() to be just zero when deparsing
an expression that's not supposed to contain variables. Per discussion
with Gevik Babakhani, this eliminates the need for an ugly kluge (namely,
specifying some unrelated relation name). Remove one such kluge from
pg_dump.
Tom Lane [Tue, 26 May 2009 02:17:50 +0000 (02:17 +0000)]
Remove the useless and rather inconsistent return values of EncodeDateOnly,
EncodeTimeOnly, EncodeDateTime, EncodeInterval. These don't have any good
reason to fail, and their callers were mostly not checking anyway.
Tom Lane [Tue, 26 May 2009 01:39:49 +0000 (01:39 +0000)]
Remove unused declarations of EncodeTimeOnly and DecodeTimeOnly.
Tom Lane [Tue, 26 May 2009 01:29:09 +0000 (01:29 +0000)]
Add range checks to time_recv() and timetz_recv(), to prevent binary input
of time values that would not be accepted via textual input.
Per gripe from Andrew McNamara.
This is potentially a back-patchable bug fix, but for the moment it doesn't
seem sufficiently high impact to justify doing that.
Tom Lane [Sun, 24 May 2009 22:22:44 +0000 (22:22 +0000)]
Use more-portable coding for the check on handing out the last available
relopt_kind value in add_reloption_kind(). Per Zdenek Kotala.
Tom Lane [Sun, 24 May 2009 18:10:38 +0000 (18:10 +0000)]
Fix LIKE's special-case code for % followed by _. I'm not entirely sure that
this case is worth a special code path, but a special code path that gets
the boundary condition wrong is definitely no good. Per bug #4821 from
Andrew Gierth.
In passing, clean up some minor code formatting issues (excess parentheses
and blank lines in odd places).
Back-patch to 8.3, where the bug was introduced.
Teodor Sigaev [Thu, 21 May 2009 20:09:36 +0000 (20:09 +0000)]
Resort tsvector's lexemes in tsvectorrecv instead of emmiting an error.
Basically, it's needed to support binary dump from 8.3 because ordering rule
was changed.
Per discussion with Bruce.
Michael Meskes [Thu, 21 May 2009 12:54:27 +0000 (12:54 +0000)]
Removed comparison of unsigned expression < 0.
Peter Eisentraut [Thu, 21 May 2009 01:08:43 +0000 (01:08 +0000)]
Convert some messages to use ngettext().
Author: Euler Taveira de Oliveira <euler@timbira.com>
Peter Eisentraut [Wed, 20 May 2009 23:51:24 +0000 (23:51 +0000)]
Fix sgml-mode example. thanks Andrew Dunstan
Michael Meskes [Wed, 20 May 2009 16:49:23 +0000 (16:49 +0000)]
Removed unsigned/signed mismatches.
Michael Meskes [Wed, 20 May 2009 16:39:56 +0000 (16:39 +0000)]
More variables gcc moans about
Michael Meskes [Wed, 20 May 2009 16:13:18 +0000 (16:13 +0000)]
Removed some unneeded variables and comparisons
Heikki Linnakangas [Wed, 20 May 2009 08:48:10 +0000 (08:48 +0000)]
Silence a gcc compiler warning about non-literal format string with no args
when compiling with -Wformat-security. Fujii Masao.
Peter Eisentraut [Tue, 19 May 2009 22:32:41 +0000 (22:32 +0000)]
Add documentation string for LDFLAGS_SL in configure --help output.
Heikki Linnakangas [Tue, 19 May 2009 08:30:00 +0000 (08:30 +0000)]
Update relpages and reltuples estimates in stand-alone ANALYZE, even if
there's no analyzable attributes or indexes. We also used to report 0 live
and dead tuples for such tables, which messed with autovacuum threshold
calculations.
This fixes bug #4812 reported by George Su. Backpatch back to 8.1.