| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
As proof of concept, provide an alternate implementation based on POSIX
semaphores. Also push the SysV shared-memory implementation into a
separate file so that it can be replaced conveniently.
|
| | |
|
| |
|
|
|
| |
only if they would not be found without qualification given the current
search path, as per idea from Peter Eisentraut.
|
| | |
|
| |
|
|
| |
from Liam Stewart. Minor code cleanups also.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
handled as special productions. This is needed to keep us honest about
user-schema type names that happen to coincide with system type names.
Per pghackers discussion 24-Apr. To avoid bloating the keyword list
too much, I removed the translations for datetime, timespan, and lztext,
all of which were slated for destruction several versions back anyway.
|
| | |
|
| |
|
|
|
|
| |
in gram.y can make use of the keywords.c string table, instead of having
their own copies of the keyword strings. This saves a few kilobytes and
more importantly eliminates an opportunity for cut-and-paste errors.
|
| |
|
|
|
|
| |
in the search path. (We might want to make these available as SQL
functions too, but I haven't done that yet.) Fix format_type to be
schema-aware.
|
| |
|
|
| |
binary case) already has. Needed for upcoming ruleutils change.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
in parse error messages, not just the part scanned by the last flex rule.
For example,
select "foo" "bar";
used to draw
ERROR: parser: parse error at or near """
which was rather unhelpful. Now it gives
ERROR: parser: parse error at or near ""bar""
Also, error messages concerning bitstring literals and suchlike will
quote the source text at you, not the processed internal form of the literal.
|
| |
|
|
|
|
|
| |
PL/PgSQL grammar, which were causing warnings when used with Bison
1.35.
Neil Conway <neilconway@rogers.com>
|
| |
|
|
| |
see changes made by the transaction itself.
|
| |
|
|
| |
in presence of schemas.
|
| | |
|
| |
|
|
|
| |
I concluded that RENAME should require CREATE privilege on the namespace
as well as ownership of the table.
|
| |
|
|
| |
don't scribble on tuple returned by table scan.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
gcc does not complain about this mistake, but other compilers do.
|
| | |
|
| |
|
|
| |
was incorrectly used for both qsort and bsearch.
|
| |
|
|
|
|
|
|
| |
lists to join RTEs, attach a list of Vars and COALESCE expressions that will
replace the join's alias variables during planning. This simplifies
flatten_join_alias_vars while still making it easy to fix up varno references
when transforming the query tree. Add regression test cases for interactions
of subqueries with outer joins.
|
| |
|
|
| |
- Fixed a typo in a comment printed by ecpg.
|
| |
|
|
| |
in quoting rules and recognition of implicit type coercions.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
pg_database, pg_shadow, pg_group, all of which now have potentially-long
fields. Along the way, get rid of SharedSystemRelationNames list: shared
rels are now identified in their include/pg_catalog/*.h files by a
BKI_SHARED_RELATION macro, while indexes and toast rels inherit sharedness
automatically from their parent table. Fix some bugs with failure to detoast
pg_group.grolist during ALTER GROUP.
|
| |
|
|
| |
pg_hba.conf changes.
|
| |
|
|
|
|
|
| |
messages more uniform and internationalizable: the global array
aclcheck_error_strings[] is gone in favor of a subroutine
aclcheck_error(). Partial implementation of namespace-related
permission checks --- not all done yet.
|
| |
|
|
|
|
|
| |
divide backend/commands by object type, let's try to pay at least
minimal attention to respecting that structure, eh? Also reorder the
contents of tablecmds.c; it seems odd to me to put ALTER commands before
creation/deletion commands.
|
| |
|
|
|
| |
Update has_table_privilege functions to cope with schema-qualified
names in the same way as nextval() and others.
|
| |
|
|
|
|
|
| |
per pghackers discussion. Add some more typsanity tests, and clean
up some problems exposed thereby (broken or missing array types for
some built-in types). Also, clean up loose ends from unknownin/out
patch.
|
| |
|
|
|
|
|
|
|
|
|
| |
by Marcelo Aceto <aceto@newinf.com.br> .
1) Wrong translations of embedded escape sequences inside outer join escape
sequences.
2) Wrong translation of parameter markers inside outer joins and function
escape sequences.
3) Bad concatenation of date, time, timestamp constants with next word in
statement:
|
| | |
|
| | |
|
| |
|
|
| |
any size now.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
dynamically with PQExpBuffer.
|
| | |
|
| | |
|
