aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* Change SC_fetch() to not retrieve data in case theHiroshi Inoue2001-10-19
| | | | | SQL_RETRIEVE_DATA option is SQL_RD_OFF. This would avoid a crash when scrolling Grid controls.
* Fix pltcl to update cached function def afterTom Lane2001-10-19
| | | | CREATE OR REPLACE FUNCTION.
* Move init_ps_display from postgres.c to postmaster.c, putting itTom Lane2001-10-19
| | | | | | | | | | | just after receipt of the startup packet. Now, postmaster children that are waiting for client authentication response will show as 'postgres: user database host authentication'. Also, do an init_ps_display for startup/shutdown/checkpoint subprocesses, so that they are readily identifiable as well. Fix an obscure race condition that could lead to Assert failure in the postmaster --- attempting to start a checkpoint process before any connections have been received led to calling PostmasterRandom before setting random_seed.
* Spell 'between' correctly, clean up spacing in error messages.Tom Lane2001-10-18
|
* 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.
* Add STATUS_EOF value needed for auth.c. Remove a bunch of unusedTom Lane2001-10-18
| | | | STATUS_xxx macros to reduce clutter.
* Fix several problems with simple_prompt() --- the nastiest being thatTom Lane2001-10-18
| | | | | | the entered password would get echoed on some platforms, eg HPUX. We have enough copies of this code that I'm thinking it ought to be moved into libpq, but that's a task for another day.
* Document all the ecpg error codes.Bruce Momjian2001-10-18
|
* Update for new expected results.Tom Lane2001-10-18
|
* 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.
* Added Lee Kindness' patches.Michael Meskes2001-10-18
|
* Make sure to clean out old activity string when recycling a backend entry.Tom Lane2001-10-16
|
* Use LEFT JOIN, not FULL JOIN, in statistical views.Tom Lane2001-10-16
|
* Updated the list of encodings supported to match what the backend now supportsBarry Lind2001-10-16
|
* Added some additional comments in the codeBarry Lind2001-10-16
|
* Python handle as string all int8 values from postgresql. This could beBruce Momjian2001-10-16
| | | | | | | | | | | | | | | view when using the aggregate function count() and function nextval that returns an int8 value, but in python is represented like string: >> db.query("select nextval('my_seq')").getresult() [('2',)] >> db.query("select count(*) from films").dictresult() [{'count': '120'}] Ricardo Caesar Lenzi
* 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
* Doesn't anyone test stuff before they commit it?Tom Lane2001-10-15
|
* > Uh, isn't the correct fixBruce Momjian2001-10-15
| | | | | | | | | | | | | | | | | | | | | | | | | > ! $$ = cat_str(8, make_str("grant"), $2, make_str("on"), $4, $5, > make_str("to"), $7, $8); > ISTM your patch loses the opt_with_grant clause. (Of course the > backend doesn't currently accept that clause anyway, but that's no > reason for ecpg to drop it.) My patch doesn't loose the option, it's never been passed on anyway: opt_with_grant: WITH GRANT OPTION { mmerror(ET_ERROR, "WITH GRANT OPTION is not supported. Only relation owners can set privileges"); } | /*EMPTY*/ ; The existing code in ecpg/preproc/preproc.y to handle the WITH option simply throws an error and aborts the processing... The patch below prevents the segfault and also passes on the WITH option to the backend, probably a better fix. Lee Kindness
* Prompt for password from /dev/tty and fall back to stdin/stderr.Bruce Momjian2001-10-15
|
* Forgot to add this file...Tatsuo Ishii2001-10-15
|
* PG_DUMP NLS (Russian)Bruce Momjian2001-10-15
| | | | | | | | Here is another one :) Another chunk of translated messages. Please apply to the same file. Serguei Mokhov
* Commit Patrice's patches except:Tatsuo Ishii2001-10-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | > - corrects a bit the UTF-8 code from Tatsuo to allow Unicode 3.1 > characters (characters with values >= 0x10000, which are encoded on > four bytes). Also, update mb/expected/unicode.out. This is necessary since the patches affetc the result of queries using UTF-8. --------------------------------------------------------------- Hi, I should have sent the patch earlier, but got delayed by other stuff. Anyway, here is the patch: - most of the functionality is only activated when MULTIBYTE is defined, - check valid UTF-8 characters, client-side only yet, and only on output, you still can send invalid UTF-8 to the server (so, it's only partly compliant to Unicode 3.1, but that's better than nothing). - formats with the correct number of columns (that's why I made it in the first place after all), but only for UNICODE. However, the code allows to plug-in routines for other encodings, as Tatsuo did for the other multibyte functions. - corrects a bit the UTF-8 code from Tatsuo to allow Unicode 3.1 characters (characters with values >= 0x10000, which are encoded on four bytes). - doesn't depend on the locale capabilities of the glibc (useful for remote telnet). I would like somebody to check it closely, as it is my first patch to pgsql. Also, I created dummy .orig files, so that the two files I created are included, I hope that's the right way. Now, a lot of functionality is NOT included here, but I will keep that for 7.3 :) That includes all string checking on the server side (which will have to be a bit more optimised ;) ), and the input checking on the client side for UTF-8, though that should not be difficult. It's just to send the strings through mbvalidate() before sending them to the server. Strong checking on UTF-8 strings is mandatory to be compliant with Unicode 3.1+ . Do I have time to look for a patch to include iso-8859-15 for 7.2 ? The euro is coming 1. january 2002 (before 7.3 !) and over 280 millions people in Europe will need the euro sign and only iso-8859-15 and iso-8859-16 have it (and unfortunately, I don't think all Unices will switch to Unicode in the meantime).... err... yes, I know that this is not every single person in Europe that uses PostgreSql, so it's not exactly 280m, but it's just a matter of time ! ;) I'll come back (on pgsql-hackers) later to ask a few questions regarding the full unicode support (normalisation, collation, regexes,...) on the server side :) Here is the patch ! Patrice. -- Patrice HÉDÉ ------------------------------- patrice à islande org ----- -- Isn't it weird how scientists can imagine all the matter of the universe exploding out of a dot smaller than the head of a pin, but they can't come up with a more evocative name for it than "The Big Bang" ? -- What would _you_ call the creation of the universe ? -- "The HORRENDOUS SPACE KABLOOIE !" - Calvin and Hobbes ------------------------------------------ http://www.islande.org/ -----
* Add UTF-8 char >= 0x10000 checkTatsuo Ishii2001-10-15
|
* Synchronize with main parser's keyword list (someone didn't check hisTom Lane2001-10-15
| | | | last commit very carefully...)
* - Fixed GRANT statement.Michael Meskes2001-10-14
| | | | - Synced preproc.y with gram.y.
* 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.
* Fix logic in insert() function.Peter Eisentraut2001-10-13
|
* Fixing closed-path intersection logic causes this test to find moreTom Lane2001-10-13
| | | | streets than it used to...
* 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.
* Add missing prototype to suppress gcc warning.Tom Lane2001-10-13
|
* Residual cleanup from making pltcl unknown support always enabled.Tom Lane2001-10-13
|
* Here are few more translated messages into RussianBruce Momjian2001-10-13
| | | | | | | | for the PG_DUMP component. Please apply to </src/bin/pg_dump/ru.po> Serguei A. Mokhov
* Attached patch for unconditional enabling of pltcl-unknown support.Bruce Momjian2001-10-13
| | | | | | | | Enabling this feature adds very light overhead of 1 select from pg_class on first using of pl/tcl in backend if unknown suppport is really unused. But pl/tcl with this support has very improved functionality. Patch includes changes to documentation.
* Mention createlang when language not installed, per problem report.Bruce Momjian2001-10-13
|
* Update the version of psqlodbc driver.Hiroshi Inoue2001-10-12
|
* 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.
* Fix the bug reported by Chris Lee.Hiroshi Inoue2001-10-12
|
* 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
|
* Tatsuo Ishii <t-ishii@sra.co.jp> writes:Bruce Momjian2001-10-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | > As you can see, psql reconnect as any user if the password is same as > foo. Of course this is due to the careless password setting, but I > think it's better to prompt ANY TIME the user tries to switch to > another user. Comments? Yeah, I agree. Looks like a simple change in dbconnect(): /* * Use old password if no new one given (if you didn't have an old * one, fine) */ if (!pwparam && oldconn) pwparam = PQpass(oldconn); to /* * Use old password (if any) if no new one given and we are * reconnecting as same user */ if (!pwparam && oldconn && PQuser(oldconn) && userparam && strcmp(PQuser(oldconn), userparam) == 0) pwparam = PQpass(oldconn); regards, tom lane
* 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.
* This patch fixes a bug introduced in the jdbc bytea support patch.Barry Lind2001-10-09
| | | | | | | | | | | | | | That patch broke the ability to read data from binary cursors. --Barry Lind Modified Files: pgsql/src/interfaces/jdbc/org/postgresql/Connection.java pgsql/src/interfaces/jdbc/org/postgresql/ResultSet.java pgsql/src/interfaces/jdbc/org/postgresql/core/QueryExecutor.java pgsql/src/interfaces/jdbc/org/postgresql/jdbc1/Connection.java pgsql/src/interfaces/jdbc/org/postgresql/jdbc1/ResultSet.java pgsql/src/interfaces/jdbc/org/postgresql/jdbc2/Connection.java pgsql/src/interfaces/jdbc/org/postgresql/jdbc2/ResultSet.java pgsql/src/interfaces/jdbc/org/postgresql/jdbc2/UpdateableResultSet.java
* Change plpgsql compiler so that all elogs are trapped and a suitableTom Lane2001-10-09
| | | | | | | NOTICE added about error location (same method already used by plpgsql executor). Add checking of pg_proc row xmin/cmin to ensure that plpgsql functions will be recompiled after they've been modified by CREATE OR REPLACE FUNCTION.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-03 20:28:23 +0000