| Commit message (Collapse) | Author | Age |
|
|
|
| |
files being left around.
|
|
|
|
|
| |
coerce_type, so that the right things happen when coercing a previously-
unknown constant to a destination data type.
|
|
|
|
| |
and elog(ERROR) inside bufmgr.
|
|
|
|
|
|
| |
SQL cast constructs can be performed during expression transformation
instead of during parsing. This allows constructs like x::numeric(9,2)
and x::int2::float8 to behave as one would expect.
|
|
|
|
|
|
|
|
|
| |
read is reused for successive attributes, instead of being deleted and
recreated from scratch for each value read in. This reduces palloc/pfree
overhead a lot. COPY IN still seems to be noticeably slower than it was
in 6.5 --- we need to figure out why. This change takes care of the only
major performance loss I can see in copy.c itself, so the performance
problem is at a lower level somewhere.
|
| |
|
|
|
|
|
|
| |
CommandCounterIncrement to make new relation visible before trying to
parse/deparse the expressions. Also, eliminate unnecessary
setheapoverride calls in AddNewAttributeTuples.
|
| |
|
| |
|
|
|
|
|
| |
the case wherein zero was rejected for a field like NUMERIC(4,4).
Miscellaneous other code beautification efforts.
|
|
|
|
|
|
|
| |
functions, which would lead to trouble with datatypes that paid attention
to the typelem or typmod parameters to these functions. In particular,
incorrect code in pg_aggregate.c explains the platform-specific failures
that have been reported in NUMERIC avg().
|
|
|
|
|
|
| |
- Prevent permissions on indexes
- Instituted --enable-multibyte option and tweaked the MB build process where necessary
- initdb prompts for superuser password
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Let unprivileged users change their own passwords.
* The password is now an Sconst in the parser, which better reflects its text datatype and also
forces users to quote them.
* If your password is NULL you won't be written to the password file, meaning you can't connect
until you have a password set up (if you use password authentication).
* When you drop a user that owns a database you get an error. The database is not gone.
|
|
|
|
|
|
| |
choke on relation or attribute names containing spaces, quotes, or other
special characters. This fixes a TODO item. It also forces initdb,
since stored rule strings change.
|
|
|
|
| |
error-proof. Rearranged some old code and removed dead sections.
|
|
|
|
|
| |
Update README so that it reflects all source file names
Add an entry to make sjistest (testing between SJIS/EUC_JP conversion)
|
| |
|
|
|
|
| |
on FUNC_MAX_ARGS by using an appropriate fmgr() call.
|
| |
|
| |
|
| |
|
|
|
|
| |
in indexkeys, classlist arrays.
|
| |
|
| |
|
|
|
|
| |
and int2vector.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
properly.
|
|
|
|
|
|
| |
this would fix TODO
* elog() flushes cache, try invalidating just entries from
current xact, perhaps using invalidation cache
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
errors. VACUUM normally compacts the table back-to-front, and stops
as soon as it gets to a page that it has moved some tuples onto.
(This logic doesn't make for a complete packing of the table, but it
should be pretty close.) But the way it was checking whether it had
got to a page with some moved-in tuples was to look at whether the
current page was the same as the last page of the list of pages that
have enough free space to be move-in targets. And there was other
code that would remove pages from that list once they got full.
There was a kluge that prevented the last list entry from being
removed, but it didn't get the job done. Fixed by keeping a separate
variable that contains the largest block number into which a tuple
has been moved. There's no longer any need to protect the last element
of the fraged_pages list.
Also, fix NOTICE messages to describe elapsed user/system CPU time
correctly.
|
| |
|
|
|
|
|
|
| |
postmaster/postmaster.c so that
tcop/postgres.c can use them. Now we have an interlock between
postmaster and postgres.
|
|
|
|
|
| |
tcop/postgres.c can use them. Now we have an interlock between
postmaster and postgres.
|
|
|
|
|
| |
code cleanup; no major improvements yet. However, EXPLAIN does produce
more intuitive outputs for nested loops with indexscans now...
|
|
|
|
| |
as well as when inserting entries into an existing index.
|
|
|
|
|
|
|
|
|
| |
still
without answer. I want continue with to_char(), but I need any answer
for this patch. Please.
Thank! (and sorry of my impatient :-)
Karel
|
| |
|