aboutsummaryrefslogtreecommitdiff
path: root/src/backend
Commit message (Collapse)AuthorAge
...
* Fix memory leakage when sending notice messages to client.Tom Lane2001-10-18
|
* Fix authentication so that it doesn't record an extra 'PasswordTom Lane2001-10-18
| | | | | | | | | | authentication failed' and a 'send() failed: Broken pipe' message on every connection from psql in password auth mode. Problem is that psql doesn't ask user for a password until it sees a password challenge failure, and libpq just closes the connection unceremoniously if it's challenged for a password when it hasn't got one to send. Accordingly, EOF from the client after asking for a password is normal behavior and should not result in postmaster log entries.
* Didn't compile on non-HAVE_TM_ZONE machines.Tom Lane2001-10-18
|
* Repair missing brace in HAVE_INT_TIMEZONE case.Tom Lane2001-10-18
|
* Accept an INTERVAL argument for SET TIME ZONE per SQL99.Thomas G. Lockhart2001-10-18
| | | | | | | | | | | | | | | | | | | | | | | | | Modified the parser and the SET handlers to use full Node structures rather than simply a character string argument. Implement INTERVAL() YEAR TO MONTH (etc) syntax per SQL99. Does not yet accept the goofy string format that goes along with, but this should be fairly straight forward to fix now as a bug or later as a feature. Implement precision for the INTERVAL() type. Use the typmod mechanism for both of INTERVAL features. Fix the INTERVAL syntax in the parser: opt_interval was in the wrong place. INTERVAL is now a reserved word, otherwise we get reduce/reduce errors. Implement an explicit date_part() function for TIMETZ. Should fix coersion problem with INTERVAL reported by Peter E. Fix up some error messages for date/time types. Use all caps for type names within message. Fix recently introduced side-effect bug disabling 'epoch' as a recognized field for date_part() etc. Reported by Peter E. (??) Bump catalog version number. Rename "microseconds" current transaction time field from ...Msec to ...Usec. Duh! date/time regression tests updated for reference platform, but a few changes will be necessary for others.
* Extend code that deduces implied equality clauses to detect whether aTom Lane2001-10-18
| | | | | | | | clause being added to a particular restriction-clause list is redundant with those already in the list. This avoids useless work at runtime, and (perhaps more importantly) keeps the selectivity estimation routines from generating too-small estimates of numbers of output rows. Also some minor improvements in OPTIMIZER_DEBUG displays.
* Make sure to clean out old activity string when recycling a backend entry.Tom Lane2001-10-16
|
* Ok, here is the modified encoding table (column1 is the standard name,Tatsuo Ishii2001-10-16
| | | | | | | | | | | | | | | | | | | | | | | 2 is our "official" name, and 3 is alias). If there's no objection, I will change them. ASCII SQL_ASCII UTF-8 UNICODE UTF_8 MULE-INTERNAL MULE_INTERNAL ISO-8859-1 LATIN1 ISO_8859_1 ISO-8859-2 LATIN2 ISO_8859_2 ISO-8859-3 LATIN3 ISO_8859_3 ISO-8859-4 LATIN4 ISO_8859_4 ISO-8859-5 ISO_8859_5 ISO-8859-6 ISO_8859_6 ISO-8859-7 ISO_8859_7 ISO-8859-8 ISO_8859_8 ISO-8859-9 LATIN5 ISO_8859_9 ISO-8859-10 LATIN6 ISO_8859_10 ISO-8859-13 LATIN7 ISO_8859_13 ISO-8859-14 LATIN8 ISO_8859_14 ISO-8859-15 LATIN9 ISO_8859_15 ISO-8859-16 LATIN10 ISO_8859_16
* Add UTF-8 char >= 0x10000 checkTatsuo Ishii2001-10-15
|
* Make selectivity routines cope gracefully with NaNs, infinities, andTom Lane2001-10-13
| | | | | NUMERIC values that are out of the range of 'double'. Per trouble report from Mike Quinn.
* path_inter, path_distance, path_length, dist_ppath now do the rightTom Lane2001-10-13
| | | | | things with closed paths --- ie, include the closing line segment in their calculations. Per bug report from Curtis Barrett 9-Oct-01.
* Mention createlang when language not installed, per problem report.Bruce Momjian2001-10-13
|
* Add a new function "pg_client_encoding" which returns the current clientTatsuo Ishii2001-10-12
| | | | | | side encoding name. This is necessary for client API's such as JDBC to perform correct encoding conversions. See my email "[HACKERS] pg_client_encoding" 10 Sep 2001.
* Break transformCreateStmt() into multiple routines and makeTom Lane2001-10-12
| | | | | | | | | transformAlterStmt() use these routines, instead of having lots of duplicate (not to mention should-have-been-duplicate) code. Adding a column with a CHECK constraint actually works now, and the tests to reject unsupported DEFAULT and NOT NULL clauses actually fire now. ALTER TABLE ADD PRIMARY KEY works, modulo having to have created the column(s) NOT NULL already.
* Suppress gcc warnings.Tom Lane2001-10-11
|
* Add support for ISO-8859-6 to 16Tatsuo Ishii2001-10-11
|
* Remove gratuitous discrepancy between extract() and date_part(),Peter Eisentraut2001-10-10
| | | | | regarding timezone_hour, timezone_minute vs. tz_hour, tz_minute. Document the former.
* Allow optional () after current_user, session_user, user, current_time,Peter Eisentraut2001-10-09
| | | | | | | | | current_timestamp, current_date for ODBC compatibility. Add more functions to odbc.sql catalog extension, use new CREATE OR REPLACE FUNCTION. Document iODBC/unixODBC build options.
* Fix typo in error message. Noted by laser@zhengmai.com.cn.Tom Lane2001-10-09
|
* Change plpgsql to depend on main parser's type-declaration grammar,Tom Lane2001-10-09
| | | | | | | rather than having its own somewhat half-baked notion of what a type declaration looks like. This is necessary now to ensure that plpgsql will think a 'timestamp' variable has the same semantics as 'timestamp' does in the main SQL grammar; and it should avoid divergences in future.
* Another go-round with FigureColname, to produce less surprising resultsTom Lane2001-10-08
| | | | | | for nested typecasts. It now produces a column header of 'timestamptz' for 'SELECT CURRENT_TIMESTAMP', rather than 'text' as it was doing for awhile there.
* Fix transformExpr() to not scribble on its input datastructure whileTom Lane2001-10-08
| | | | | transforming CASE expressions. This was definitely confusing FigureColname, and might lead to bad things elsewhere as well.
* Fix ruleutils to depend on format_type, rather than having a privateTom Lane2001-10-08
| | | | | copy of code that knows about displaying types with typmod info. Needed so that it does the right thing with timestamp datatypes now.
* Make ALTER TABLE RENAME COLUMN update column names of indexes thatTom Lane2001-10-08
| | | | refer to the renamed column. Brent Verner, with a little help from tgl.
* Remove redundant code, update comments, cause CURRENT_TIME toTom Lane2001-10-08
| | | | agree with CURRENT_TIME(n).
* Rearrange fmgr.c and relcache so that it's possible to keep FmgrInfoTom Lane2001-10-06
| | | | | | | | | lookup info in the relcache for index access method support functions. This makes a huge difference for dynamically loaded support functions, and should save a few cycles even for built-in ones. Also tweak dfmgr.c so that load_external_function is called only once, not twice, when doing fmgr_info for a dynamically loaded function. All per performance gripe from Teodor Sigaev, 5-Oct-01.
* files attached are Traditional Chinese translations translatedBruce Momjian2001-10-05
| | | | | | | and modified from Simplified Chinese translations for backend, pgsql, pg_dump and libpq. I've appended their names to zh_TW.po. forth
* Further cleanup of dynahash.c API, in pursuit of portability andTom Lane2001-10-05
| | | | | | | | | readability. Bizarre '(long *) TRUE' return convention is gone, in favor of just raising an error internally in dynahash.c when we detect hashtable corruption. HashTableWalk is gone, in favor of using hash_seq_search directly, since it had no hope of working with non-LONGALIGNable datatypes. Simplify some other code that was made undesirably grotty by promixity to HashTableWalk.
* > > I am quite sure that all AIX Versions accept the CLOBBER method,Bruce Momjian2001-10-05
| | | | | | > > thus I ask you to apply the following patch, to make it work. Zeugswetter Andreas SB SD
* Define CEST as a synonym for Central European Savings TimeThomas G. Lockhart2001-10-05
| | | | | per Jan Varga <varga@utcru.sk> Fix up spacing and formatting.
* Implement explicit date/time precision per SQL99 spec.Thomas G. Lockhart2001-10-05
| | | | Use CAST() mechanism to define CURRENT_TIME and CURRENT_TIMESTAMP.
* Consider interpreting a function call as a trivial (binary-compatible)Tom Lane2001-10-04
| | | | | | | | | type coercion after failing to find an exact match in pg_proc, but before considering interpretations that involve a function call with one or more argument type coercions. This avoids surprises wherein what looks like a type coercion is interpreted as coercing to some third type and then to the destination type, as in Dave Blasby's bug report of 3-Oct-01. See subsequent discussion in pghackers.
* Ooops, I was a little too enthusiastic about suppressing defaultTom Lane2001-10-04
| | | | | index opclasses; they might be default for some other datatype, in which case we mustn't suppress 'em.
* Plug memory leaks introduced by dynamic-search-path changes.Tom Lane2001-10-04
| | | | From Teodor Sigaev.
* Make the world safe for atttypmod=0 ... this didn't use to mean anything,Tom Lane2001-10-04
| | | | but timestamp now wants it to mean something.
* Make current_time deliver a fractional-second answer.Tom Lane2001-10-04
|
* I've just finished the Chinese NLS support(zh_CN part) filesBruce Momjian2001-10-04
| | | | | | | | | translation, the attachement is those four files. (.tar.gz file, with the directory, root is $PGSRC). Tested on some Linux platform. Weiping He
* Attached please find an initiation of theBruce Momjian2001-10-04
| | | | | | | | | | | | | | | | | NLS effort for the 'postgresql' component. It includes 'ru.po', which should be added to /src/backend/po/ and a typical patch for nls.mk with the 'ru' entry added in the AVAIL_LANGUAGES. I'll submit a patch with more translations for pg_dump once CVSweb becomes available. CVSweb for me right now is the only way to get to the source code until my system is completely setup by the end of the week. -- Serguei A. Mokhov
* AdjustTimeForTypmod has the same bug ...Tom Lane2001-10-04
|
* Fix some problems in new variable-resolution-timestamp code.Tom Lane2001-10-04
|
* Add dependency for regexec.cTatsuo Ishii2001-10-04
|
* Add dependency for like.cTatsuo Ishii2001-10-04
|
* Optimization for single byte encodings.Tatsuo Ishii2001-10-04
|
* Consistently use gcc's __attribute__((format)) to check sprintf-styleTom Lane2001-10-03
| | | | | format strings wherever possible. Remarkably, this exercise didn't turn up any inconsistencies, but it seems a good idea for the future.
* DROP AGGREGATE and COMMENT ON AGGREGATE now accept the expected syntaxTom Lane2001-10-03
| | | | | | | 'aggname (aggtype)'. The old syntax 'aggname aggtype' is still accepted for backwards compatibility. Fix pg_dump, which was actually broken for most cases of user-defined aggregates. Clean up error messages associated with these commands.
* Teach format_type about time/timestamp precision, so that pg_dump andTom Lane2001-10-03
| | | | psql's \d option work properly.
* Add missing TIMESTAMPTZ case.Tom Lane2001-10-03
|
* AdjustTimestampForTypmod does not work (at least not portably) onTom Lane2001-10-03
| | | | | | -infinity and +infinity. Put TIMESTAMP_NOT_FINITE guard into the routine, instead of forgetting it at some call sites. Fixes regression test failures here.
* Implement precision support for timestamp and time, both with and withoutThomas G. Lockhart2001-10-03
| | | | | | | | | | | | time zones. SQL99 spec requires a default of zero (round to seconds) which is set in gram.y as typmod is set in the parse tree. We *could* change to a default of either 6 (for internal compatibility with previous versions) or 2 (for external compatibility with previous versions). Evaluate entries in pg_proc wrt the iscachable attribute for timestamp and other date/time types. Try to recognize cases where side effects like the current time zone setting may have an effect on results to decide whether something is cachable or not.
* Add CREATE OR REPLACE FUNCTION syntax to allow replacing a functionTom Lane2001-10-02
| | | | | definition without changing the function's OID, thereby not breaking rules, views, triggers, etc that depend on it. From Gavin Sherry.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-08 08:56:00 +0000