| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |
|
|
| |
error sqlstate. This change makes it return a correct value..
|
| |
|
|
|
|
| |
with binary compatibility.
Backpatch to 8.4 where INOUT casts were introduced.
|
| | |
|
| |
|
|
|
|
|
| |
about the behavior.
Document that quotes in to_date, to_timestamp, to_number skip input
characters.
|
| |
|
|
|
|
|
| |
set ferror() but never set feof(). This is known to be the case for recent
glibc when trying to read a directory as a file, and might be true for other
platforms/cases too. Per report from Ed L. (There is more that we ought to
do about his report, but this is one easily identifiable issue.)
|
| |
|
|
| |
privileges of foreign servers is "GRANT ... ON *FOREIGN* SERVER ...".
|
| |
|
|
|
|
|
|
|
| |
too, instead of duplicating the functionality (badly).
I renamed xml_init to pg_xml_init, because the former seemed just a bit too
generic to be safe as a global symbol. I considered likewise renaming
xml_ereport to pg_xml_ereport, but felt that the reference to ereport probably
made it sufficiently PG-centric already.
|
| | |
|
| |
|
|
|
|
|
|
| |
section, throw an error message saying explicitly that the label must go
before DECLARE. Per investigation of a recent pgsql-novice question,
this code did not work as intended in any modern PG version, maybe not ever.
Allowing such a thing would only create ambiguity anyway, so it seems better
to remove it than fix it.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Per bug #5352, this helps to provide a useful error message if the user
tries to do something presently unsupported, namely use a rowtype variable
as a member of a multiple-item INTO list.
|
| | |
|
| |
|
|
| |
but not in cells).
|
| |
|
|
|
|
|
|
|
|
| |
formats; a null string must not be formatted as a numeric. The more exotic
formats latex and troff also incorrectly formatted all strings as numerics
when numericlocale was on.
Backpatch to 8.1 where numericlocale option was added.
This fixes bug #5355 reported by Andy Lester.
|
| |
|
|
|
| |
since we released a version without it, so remove the comment that
says we might want to do that.
|
| | |
|
| |
|
|
| |
based on Vista results
|
| |
|
|
| |
build farm says of opening directories read-only and ignoring EBADF from fsync of directories
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
the fact that NetBSD/mips is currently broken, as per buildfarm member pika.
Also add regression tests to ensure that get_float8_nan and get_float4_nan
are exercised even on platforms where they are not needed by
float8in/float4in.
Zoltán Böszörményi and Tom Lane
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
regession test output, and update pgindent script to avoid them in the
future.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We had originally made the stronger assumption that NOT A refutes any B
if B implies A, but this fails in three-valued logic, because we need to
prove B is false not just that it's not true. However the logic does
go through if B is equal to A.
Recognizing this limited case is enough to handle examples that arise when
we have simplified "bool_var = true" or "bool_var = false" to just "bool_var"
or "NOT bool_var". If we had not done that simplification then the
btree-operator proof logic would have been able to prove that the expressions
were contradictory, but only for identical expressions being compared to the
constants; so handling identical A and B covers all the same cases.
The motivation for doing this is to avoid unexpected asymmetrical behavior
when a partitioned table uses a boolean partitioning column, as in today's
gripe from Dominik Sander.
Back-patch to 8.2, which is as far back as predicate_refuted_by attempts to
do anything at all with NOTs.
|
| | |
|
| |
|
|
|
|
|
|
| |
how often we do SSL session key renegotiation. Can be set to
0 to disable renegotiation completely, which is required if
a broken SSL library is used (broken patches to CVE-2009-3555
a known cause) or when using a client library that can't do
renegotiation.
|
| |
|
|
| |
Per complaint from Greg Stark.
|
| |
|
|
|
|
| |
error cases less intimidating for novices. Per discussion.
Greg Smith
|
| |
|
|
|
| |
a desirable fashion in archive-dump cases, ie you should get the pg_dump
version not the pg_restore version.
|
| |
|
|
|
|
| |
This was evidently broken by the CREATE TABLE OF TYPE patch. It would have
been noticed if anyone had bothered to try dumping and restoring the
regression database ...
|
| |
|
|
|
| |
significantly uglier kluges that were working around the change in plpgsql's
preinstalled status.
|
| |
|
|
|
|
| |
will work whether or not the specified language is preinstalled. This
responds to some complaints about having to change test scripts because
plpgsql is preinstalled as of 9.0.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This operates in the same way as other CREATE OR REPLACE commands, ie,
it replaces everything but the ownership and ACL lists of an existing
entry, and requires the caller to have owner privileges for that entry.
While modifying an existing language has some use in development scenarios,
in typical usage all the "replaced" values come from pg_pltemplate so there
will be no actual change in the language definition. The reason for adding
this is mainly to allow programs to ensure that a language exists without
triggering an error if it already does exist.
This commit just adds and documents the new option. A followon patch
will use it to clean up some unpleasant cases in pg_dump and pg_regress.
|
| |
|
|
|
|
| |
text output mode, like we do in custom output mode.
Jim Cox
|
| |
|
|
|
|
|
| |
"dumping data out of order is not supported" to "restoring data out of order
is not supported", because you get that error during pg_restore not pg_dump.
Also fix some comments that didn't look so good after being pgindented as
perhaps they did originally.
|
| |
|
|
| |
improve documentation, and add C comment.
|
| | |
|
| | |
|
