summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* This patch implements putting language handlers for the optional PLsBruce Momjian2005-07-104-47/+125
| | | | | | | | | | | | | | | | into pg_catalog rather than public, and supports dumping languages whose handlers are found there. This will make it easier to drop the public schema if desired. Unlike the previous patch, the comments have been updated and I have reformatted some code to meet Alvarro's request to stick to 80 cols. (I actually aghree with this - it makes printing the code much nicer). I think I did the right thing w.r.t versions earlier than 7.3, but I have no real way of checking, so that should be checked by someone with more/older knowledge than me ;-) Andrew Dunstan
* As Kris Jurka found out, pgcrypto does not work withBruce Momjian2005-07-101-18/+38
| | | | | | | | | | | | | | | | | | | | | | | | | OpenSSL 0.9.6x. The DES functions use the older 'des_' API, but the newer 3DES functions use the 0.9.7x-only 'DES_' API. I think I just used /usr/include/openssl/des.h for reference when implementing them, and had upgraded OpenSSL in the meantime. Following patch converts DES also to newer API and provides compatibility functions for OpenSSL < 0.9.7. I chose this route because: - openssl.c uses few DES functions. - compatibility for old 'des_' API is going away at some point of time from OpenSSL. - as seen from macros, new API is saner - Thus pgcrypto supports any OpenSSL version from 0.9.5 to 1.0 Tested with OpenSSL 0.9.6c and 0.9.7e. Marko Kreen
* Add missing pgcrypto files from previous commit.Bruce Momjian2005-07-1044-0/+10539
|
* Update.Bruce Momjian2005-07-102-9/+4
| | | | | | | | < computations should adjust based on the time zone rules, e.g. < adding 24 hours to a timestamp would yield a different result from < adding one day. < > computations should adjust based on the time zone rules.
* This patch addresses the problem mentioned in the "process crashBruce Momjian2005-07-107-4/+100
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | when a plpython function returns unicode" thread: http://archives.postgresql.org/pgsql-bugs/2005-06/msg00105.php In several places PL/Python was calling PyObject_Str() and then PyString_AsString() without checking if the former had returned NULL to indicate an error. PyString_AsString() doesn't expect a NULL argument, so passing one causes a segmentation fault. This patch adds checks for NULL and raises errors via PLy_elog(), which prints details of the underlying Python exception. The patch also adds regression tests for these checks. All tests pass on my Solaris 9 box running HEAD and Python 2.4.1. In one place the patch doesn't call PLy_elog() because that could cause infinite recursion; see the comment I added. I'm not sure how to test that particular case or whether it's even possible to get an error there: the value that the code should check is the Python exception type, so I wonder if a NULL value "shouldn't happen." This patch converts NULL to "Unknown Exception" but I wonder if an Assert() would be appropriate. The patch is against HEAD but the same changes should be applied to earlier versions because they have the same problem. The patch might not apply cleanly against earlier versions -- will the committer take care of little differences or should I submit different versions of the patch? Michael Fuhr
* I made the patch that implements regexp_replace again.Bruce Momjian2005-07-1010-55/+418
| | | | | | | | | | | | | | | | | | | | | | | The specification of this function is as follows. regexp_replace(source text, pattern text, replacement text, [flags text]) returns text Replace string that matches to regular expression in source text to replacement text. - pattern is regular expression pattern. - replacement is replace string that can use '\1'-'\9', and '\&'. '\1'-'\9': back reference to the n'th subexpression. '\&' : entire matched string. - flags can use the following values: g: global (replace all) i: ignore case When the flags is not specified, case sensitive, replace the first instance only. Atsushi Ogawa
* Major pgcrypto changes:Bruce Momjian2005-07-105-17/+408
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | of password-based encryption from RFC2440 (OpenPGP). The goal of this code is to be more featureful encryption solution than current encrypt(), which only functionality is running cipher over data. Compared to encrypt(), pgp_encrypt() does following: * It uses the equvialent of random Inital Vector to get cipher into random state before it processes user data * Stores SHA-1 of the data into result so any modification will be detected. * Remembers if data was text or binary - thus it can decrypt to/from text data. This was a major nuisance for encrypt(). * Stores info about used algorithms with result, so user needs not remember them - more user friendly! * Uses String2Key algorithms (similar to crypt()) with random salt to generate full-length binary key to be used for encrypting. * Uses standard format for data - you can feed it to GnuPG, if needed. Optional features (off by default): * Can use separate session key - user data will be encrypted with totally random key, which will be encrypted with S2K generated key and attached to result. * Data compression with zlib. * Can convert between CRLF<->LF line-endings - to get fully RFC2440-compliant behaviour. This is off by default as pgcrypto does not know the line-endings of user data. Interface is simple: pgp_encrypt(data text, key text) returns bytea pgp_decrypt(data text, key text) returns text pgp_encrypt_bytea(data bytea, key text) returns bytea pgp_decrypt_bytea(data bytea, key text) returns bytea To change parameters (cipher, compression, mdc): pgp_encrypt(data text, key text, parms text) returns bytea pgp_decrypt(data text, key text, parms text) returns text pgp_encrypt_bytea(data bytea, key text, parms text) returns bytea pgp_decrypt_bytea(data bytea, key text, parms text) returns bytea Parameter names I lifted from gpg: pgp_encrypt('message', 'key', 'compress-algo=1,cipher-algo=aes256') For text data, pgp_encrypt simply encrypts the PostgreSQL internal data. This maps to RFC2440 data type 't' - 'extenally specified encoding'. But this may cause problems if data is dumped and reloaded into database which as different internal encoding. My next goal is to implement data type 'u' - which means data is in UTF-8 encoding by converting internal encoding to UTF-8 and back. And there wont be any compatibility problems with current code, I think its ok to submit this without UTF-8 encoding by converting internal encoding to UTF-8 and back. And there wont be any compatibility problems with current code, I think its ok to submit this without UTF-8 support. Here is v4 of PGP encrypt. This depends on previously sent Fortuna-patch, as it uses the px_add_entropy function. - New function: pgp_key_id() for finding key id's. - Add SHA1 of user data and key into RNG pools. We need to get randomness from somewhere, and it is in user best interests to contribute. - Regenerate pgp-armor test for SQL_ASCII database. - Cleanup the key handling so that the pubkey support is less hackish. Marko Kreen
* - Add Fortuna PRNG to pgcrypto.Bruce Momjian2005-07-105-77/+284
| | | | | | | | | | | - Move openssl random provider to openssl.c and builtin provider to internal.c - Make px_random_bytes use Fortuna, instead of giving error. - Retarget random.c to aquiring system randomness, for initial seeding of Fortuna. There is ATM 2 functions for Windows, reader from /dev/urandom and the regular time()/getpid() silliness. Marko Kreen
* This patch adds implementation of SHA2 to pgcrypto.Bruce Momjian2005-07-102-4/+209
| | | | | | New hashes: SHA256, SHA384, SHA512. Marko Kreen
* Add psql \pset numericsep to allow output numbers like 100,000.0 orBruce Momjian2005-07-105-87/+308
| | | | | | 100.000,0. Eugen Nedelcu
* Fix inadequate error checking: you can't assume that fcinfo->resultinfoTom Lane2005-07-092-41/+45
| | | | is a ReturnSetInfo unless you've tested it with IsA.
* Fix config file lexer to not barf if postgresql.conf ends with a commentTom Lane2005-07-081-2/+2
| | | | that has no terminating newline. Per report from maps.on at gmx.net.
* Try connecting to both postgres and template1 databases to do the initialTom Lane2005-07-081-28/+46
| | | | | | | | | inspection of shared catalogs. This allows pg_dumpall to continue to work with pre-8.1 servers that likely won't have a database named postgres. Also, suppress output of SYSID options for users and groups, since server no longer does anything with these except emit a rude message. There is much more to be done to update pg_dumpall for the roles feature, but this at least makes it usable again. Per gripe from Chris K-L.
* Make libpq_gettext save and restore errno in a Windows-compatible way.Tom Lane2005-07-081-1/+5
| | | | Also, back-patch fix into back branches.
* testing activitymailPostgreSQL Daemon2005-07-081-1/+1
|
* This patch updates the DDL for contrib/pgcrypto to create allNeil Conway2005-07-081-14/+14
| | | | | | | | | | | | functions as STRICT, and all functions except gen_salt() as IMMUTABLE. gen_salt() is VOLATILE. Although the functions are now STRICT, I left their PG_ARGISNULL() checks in place as a protective measure for users who install the new code but use old (non-STRICT) catalog entries (e.g., restored from a dump). Per recent discussion in pgsql-hackers. Patch from Michael Fuhr.
* Remove some dead code for handling XLOG_DBASE_CREATE_OLD andNeil Conway2005-07-083-103/+6
| | | | | | XLOG_DBASE_DROP_OLD WAL records -- these records are no longer created in current sources. Adjust numbering of XLOG_DBASE_CREATE and XLOG_DBASE_DROP and bump the catversion. Patch from Gavin Sherry, adjusted by Neil Conway.
* Even though I'd like to see full_page_writes go away before 8.1,Tom Lane2005-07-081-5/+4
| | | | | a minimum requirement is that it not completely break the system meanwhile. Put the test in the right place.
* Done:Bruce Momjian2005-07-082-4/+4
| | | | > * -Prevent dropping user that still owns objects, or auto-drop the objects
* Track dependencies on shared objects (which is to say, roles; we alreadyTom Lane2005-07-0738-85/+1842
| | | | | | | have adequate mechanisms for tracking the contents of databases and tablespaces). This solves the longstanding problem that you can drop a user who still owns objects and/or has access permissions. Alvaro Herrera, with some kibitzing from Tom Lane.
* Update:Bruce Momjian2005-07-072-4/+8
| | | | | | | < writer. > writer. It might cause problems for applying WAL on recovery > into a partially-written page, but later the full page will be > replaced from WAL.
* Update:Bruce Momjian2005-07-072-2/+21
| | | | | | | | | | | | > > o -Add ability to turn off full page writes > o When off, write CRC to WAL and check file system blocks > on recovery > o Write full pages during file system write and not when > the page is modified in the buffer cache > > This allows most full page writes to happen in the background > writer.
* Fix plperl expected output.Bruce Momjian2005-07-071-1/+0
| | | | Andrew Dunstan
* pg_column_size() cleanup for messages and code cleanup.Bruce Momjian2005-07-071-14/+6
| | | | Mark Kirkwood
* Currently, nonfatal warnings are not trapped (as they should be) byBruce Momjian2005-07-064-2/+54
| | | | | | | | plperl - the attached small patch remedies that omission, and adds a small regression test for error and warning output - the new regression input and expected output are in separate attached files. Andrew Dunstan
* Currently, nonfatal warnings are not trapped (as they should be) byBruce Momjian2005-07-062-3/+7
| | | | | | plperl - the attached small patch remedies that omission. Andrew Dunstan
* Complete zic patch backout by removing NO_PGPORT workaround.Bruce Momjian2005-07-062-7/+7
|
* Reverse out because the lack of using pgport in timezone/ is causingBruce Momjian2005-07-065-58/+8
| | | | | | | | | | problems: --------------------------------------------------------------------------- Support cross compilation by compiling "zic" with a native compiler. This relies on the output of zic being platform independent, but that is currently the case.
* Add pg_column_size() to return storage size of a column, includingBruce Momjian2005-07-066-6/+114
| | | | | | possible compression. Mark Kirkwood
* Sync dlopen error handling for the *BSDs ... seems to me I've done thisTom Lane2005-07-063-5/+6
| | | | before, but they were out of sync again. Per Kris Jurka.
* Add a check for trigger function with declared arguments. This pathTom Lane2005-07-061-1/+8
| | | | | | | could not be reached before, but now that there is a plpgsql validator function, it can be. Check is needed to prevent core dump reported by Satoshi Nagayasu. Besides, this gives a more specific and useful error message for a fairly common novice error.
* Save and restore errno across bindtextdomain call, per discussion.Tom Lane2005-07-061-4/+12
|
* Fix incorrect PG_CPPFLAGS initialization, per Marko.Tom Lane2005-07-061-2/+2
|
* Update description of GUC full_page_writes.Bruce Momjian2005-07-061-6/+7
| | | | Michael Paesold
* Done:Bruce Momjian2005-07-062-4/+4
| | | | > * -Add function to return compressed length of TOAST data values
* Attached is a patch that enhances the "\h" capability in psql. I oftenBruce Momjian2005-07-061-38/+64
| | | | | | | | | | | | | find myself typing a command and then wanting to get the syntax for it. So I do a ctrl-a and add a \h: but psql does not recognize the command, because I have stuff attached to it (e.g. "alter table foobar"), so I have to scroll over and delete everything except the name of the command itself. This patch gives \h three chances to match: if nothing matches the complete string (current behavior), it tries to match the first two words (e.g. "ALTER TABLE"). If that fails, it tries to match the first word (e.g. "DELETE"). Greg Sabino Mullane
* Dept of second thoughts: don't expose rijndael.tbl: rijndael.c dependencyTom Lane2005-07-051-2/+2
| | | | | | to make. We ship the table file in the tarball and so this dependency just opens file timestamp skew problems without doing anything useful. (Not that it should hurt, either ... except for cross-compile builds.)
* Add GUC full_page_writes to control writing full pages to WAL.Bruce Momjian2005-07-054-5/+55
|
* Fix contrib/pgcrypto to autoconfigure for OpenSSL when --with-opensslTom Lane2005-07-054-57/+34
| | | | is used in the toplevel configure. Per Marko Kreen.
* Remove, now have GUC:Bruce Momjian2005-07-052-9/+2
| | | | | | | < * Turn off full page writes if fsync is disabled < < If fsync is off, there is no purpose in writing full pages to WAL <
* Add:Bruce Momjian2005-07-052-3/+6
| | | | | | | < 881a881,882 > o Improve xid wraparound detection by recording per-table rather > than per-database
* Back out patch. This should be done like other server-side languages.Bruce Momjian2005-07-052-28/+1
| | | | | | | | | | | | | | | | | --------------------------------------------------------------------------- This patch allows the PL/Python module to do (SRF) functions. The patch was taken from the CVS version. I have modified the plpython.c file and have added a test sql script for testing the functionality. It was actually the script that was in the 8.0.3 version but have since been removed. In order to signal the end of a set, the called python function must simply return plpy.EndOfSet and the set would be returned. Gerrit van Dyk
* Fix initialization bug in pgcrypto openssl code. Marko KreenTom Lane2005-07-053-7/+7
|
* Add NO_PGPORT defines to fix win32/cygwin builds for new target platformBruce Momjian2005-07-051-4/+4
| | | | build of zic.
* Restructure zic #define fprintf checks to use a NO_PGPORT macro instead.Bruce Momjian2005-07-043-15/+5
|
* I have to admit that I got the case of the preprocessor symbol on amd64Bruce Momjian2005-07-042-4/+4
| | | | | | wrong. __AMD64__ is not defined, __amd64__ is. Christof Petig
* This patch allows the PL/Python module to do (SRF) functions.Bruce Momjian2005-07-042-1/+28
| | | | | | | | | | | | | The patch was taken from the CVS version. I have modified the plpython.c file and have added a test sql script for testing the functionality. It was actually the script that was in the 8.0.3 version but have since been removed. In order to signal the end of a set, the called python function must simply return plpy.EndOfSet and the set would be returned. Gerrit van Dyk
* I made the patch that improved the performance of replace_text().Bruce Momjian2005-07-041-18/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The content of the patch is as follows: (1)Create shortcut when subtext was not found. (2)Stop using LEFT and RIGHT macro. In LEFT and RIGHT macro, TEXTPOS is executed by the same content as execution immediately before. The execution frequency of TEXTPOS can be reduced by using text_substring instead of LEFT and RIGHT macro. (3)Add appendStringInfoText, and use it instead of appendStringInfoString. There is an overhead of PG_TEXT_GET_STR when appendStringInfoString is executed by text type. This can be reduced by appendStringInfoText. (4)Reduce execution of TEXTDUP. The effect of the patch that I measured is as follows: - The Data for test was created by 'pgbench -i'. - Test SQL: select replace(aid, '9', 'A') from accounts; - Test results: Linux(CPU: Pentium III, Compiler option: -O2) original: 1.515s patched: 1.250s Atsushi Ogawa
* Fix compile if zic because it now doesn't use libpgport.Bruce Momjian2005-07-041-1/+11
|
* More TODO list section restructuring.Bruce Momjian2005-07-042-165/+221
|
View Lorry Controller Status