Re: [HACKERS] patch for allowing multiple -t options to pg_dump
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Scott Marlowe wrote: | On Sun, 2004-07-11 at 19:00, Bruce Momjian wrote: | |Andreas Joseph Krogh wrote: |[ PGP not available, raw data follows ] | |-BEGIN PGP SIGNED MESSAGE- |Hash: SHA1 | |Hi, I've prepared a patch(against CVS HEAD of today) to pg_dump.c to |make pg_dump understand multiple -t options for dumping multiple tables |in one command. |Eks: |pg_dump -t table1 -t table2 -t table3 dbname | |The patch is here: |http://home.officenet.no/~andreak/pg_dump.patch | |Any comments, flames? | |Is it too late for it to make it into 7.5? I submitted a patch against |7.4 a while ago, but was then told it had to wait until 7.5, and, well, |now it's 7.5-time:-) | |Uh, I see your patch posted on July 6. Is that the one? We started a |feature freeze on July 1. | | | Is this a feature or a bug fix? I'd say it's more of a bug fix, since | multiple -t switches seems like an obvious thing to support. Now, if we | were adding wild card matching that would seem like an enhancement. I | can't imagine this patch is more than a dozen lines or so. And I can't | imagine it impacting anything else going on right now. I agree that it's more a bugfix than a feature, and yes, it's not a big patch, so it should be fairy safe. - -- Andreas Joseph Krogh [EMAIL PROTECTED] Senior Software Developer / Manager gpg public_key: http://dev.officenet.no/~andreak/public_key.asc - +-+ OfficeNet AS| - a tool should do one job, and do it well. | Hoffsveien 17 | | PO. Box 425 Skøyen | | 0213 Oslo | | NORWAY | | Phone : +47 22 13 01 00 | | Direct: +47 22 13 10 03 | | Mobile: +47 909 56 963 | | - +-+ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFA8kmmUopImDh2gfQRAm3pAJ90/AXtxeZGPJpk7uEb7d6qsOCGtwCeK0+y vbZ1YMuhnxdcr4w10EKLN9A= =uSAs -END PGP SIGNATURE- ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
[HACKERS] patch for allowing multiple -t options to pg_dump
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I've prepared a patch(against CVS HEAD of today) to pg_dump.c to make pg_dump understand multiple -t options for dumping multiple tables in one command. Eks: pg_dump -t table1 -t table2 -t table3 dbname The patch is here: http://home.officenet.no/~andreak/pg_dump.patch Any comments, flames? Is it too late for it to make it into 7.5? I submitted a patch against 7.4 a while ago, but was then told it had to wait until 7.5, and, well, now it's 7.5-time:-) - -- Andreas Joseph Krogh [EMAIL PROTECTED] Senior Software Developer / Manager gpg public_key: http://dev.officenet.no/~andreak/public_key.asc - +-+ OfficeNet AS| - a tool should do one job, and do it well. | Hoffsveien 17 | | PO. Box 425 Skøyen | | 0213 Oslo | | NORWAY | | Phone : +47 22 13 01 00 | | Direct: +47 22 13 10 03 | | Mobile: +47 909 56 963 | | - +-+ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFA7ok9UopImDh2gfQRAmZRAKCUC1H0+7IA3xt9fa385VO9lX4g6wCdEkcO 2htbeud7zilIw6uMYUD35qM= =C7Cc -END PGP SIGNATURE- ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] tsearch2 patch for 7.4.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 21 November 2003 09:42, Oleg Bartunov wrote: On Fri, 21 Nov 2003, Teodor Sigaev wrote: No problem, dictionary with support of compounds will be avaliable as separate contrib module from our site till 7.5. Hmm, I think better not to introduce another dictionary, which require additional efforts to configure tsearch2, but maintain whole module with new ispell dictionary builtin. Oleg I would very much like to use this new feature, and understand if it cannot be included in tsearch2 until 7.5. The easiest way for me as a user would be if, like Oleg suggests, it would be maintained as a whole module with ispell dictionary built in and was available fro download from the tsearch2-web-site. This should be mentioned in future (pg-7.4.x)READMEs. - -- Andreas Joseph Krogh [EMAIL PROTECTED] Managing Director, Senior Software Developer OfficeNet AS - - Writing software is more fun than working. gpg public_key: http://dev.officenet.no/~andreak/public_key.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/vdIvUopImDh2gfQRAnLnAJ9uUIH1TNLms6kuKC7ptNgOHCbGlQCffzU7 1sNuWfL1PWsqbJ0xIfxo8VA= =lRte -END PGP SIGNATURE- ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
[HACKERS] pg_dump error (loading 7.2.2-dump in 7.4b4)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi. If this isn't the right list for this type of question, please redirect me to the relevant list. I get the following error trying to restore a 7.2.2-dump-file in 7.4b4: psql:nbeweb-db-as_copy-7.2.2.dmp:2051589: invalid command \nHelena psql:nbeweb-db-as_copy-7.2.2.dmp:2051589: invalid command \N psql:nbeweb-db-as_copy-7.2.2.dmp:2051589: invalid command \N The dump is created with pg_dump -O nbeweb nbeweb-db-as_copy-7.2.2.dmp This error does not occur if I dump it with pg_dump -O -D. But restoring a dump with -D takes 6 hours(dumpfile is 1.2 GB). The line in question(2051589) is here(starting with 8\t): COPY logg FROM stdin; 8 OsloHamburg 21. oktober 2002Bjørn E. Moe Hansteens gate 9, 0253 Oslo 22 31 31 62 22 55 34 23 900 90 729 22 42 50 33 [EMAIL PROTECTED] Bjørn E. M., kjønn Mann, Nasjonalitet NO\nHelena E., kjønn Kvinne, Nasjonalitet SE\n Hotel Alte Wache4 14.okt.2002 \N 3740\N 1 . . . I get several errors above the mentioned error: psql:nbeweb-db-as_copy-7.2.2.dmp:2050610: ERROR: relation on_article_searchable does not exist psql:nbeweb-db-as_copy-7.2.2.dmp:2050614: invalid command \ psql:nbeweb-db-as_copy-7.2.2.dmp:2050647: ERROR: syntax error at or near 1358 at character 1 psql:nbeweb-db-as_copy-7.2.2.dmp:2050614: invalid command \ psql:nbeweb-db-as_copy-7.2.2.dmp:2050647: ERROR: syntax error at or near 1358 at character 1 psql:nbeweb-db-as_copy-7.2.2.dmp:2050731: ERROR: syntax error at or near nei at character 1 psql:nbeweb-db-as_copy-7.2.2.dmp:2050732: ERROR: syntax error at or near ' ' at character 1 psql:nbeweb-db-as_copy-7.2.2.dmp:2051237: invalid command \N psql:nbeweb-db-as_copy-7.2.2.dmp:2051580: invalid command \. The table on_article_searchable doesn't exist 'cause I havn't installed tsearch yet(on purpose). Is it possible that pg_dump gets confused by previous errors? AFAIK, the \. command is to end a COPY table from stdin; command. I cannot risk to get partially copied tables, so the only solution seems to be to restore with a dump created with the -D option. AFAIK, \n are newlines and \N ar NULLs right? Why isnt psql able to parse it as such when restoring with COPY? It seems to think those are commands (backslash-commands), and not data. Anyone care to shed some light on this? - -- Andreas Joseph Krogh [EMAIL PROTECTED] Managing Director, Senior Software Developer OfficeNet AS - - Writing software is more fun than working. gpg public_key: http://dev.officenet.no/~andreak/public_key.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/hU3AUopImDh2gfQRAtEoAJ9FtjI/cs+ssZhGNQcV/TG0oSuRFACfYKWc fjnJEcxHpbUhv7d6IWxDcjU= =8RZH -END PGP SIGNATURE- ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[HACKERS] Patch for allowing multiple -t table-name options for pg_dump
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This si my first look at the pg-code, so it may not comply with the coding-standards. I haven't coded in C for a while either, so if someone finds a better way to implement this, go ahead, but this patch works for me with 7.4beta3. http://home.officenet.no/~andreak/pg_dump.c.diff comments are welcome. If it's ok, I'll remove my debuging statements and provide a cleaner patch. - -- Andreas Joseph Krogh [EMAIL PROTECTED] Managing Director, Senior Software Developer OfficeNet AS - - Writing software is more fun than working. gpg public_key: http://dev.officenet.no/~andreak/public_key.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/et34UopImDh2gfQRAqtBAKCcrJ3mlN5G6Jp3h3kz2G8zMlc2xgCeLmOv 844vwdmhcU4/VLjugW+ISF8= =/hYF -END PGP SIGNATURE- ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[HACKERS] free(3)-ing variables in pg_dump
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi. I'm trying to implement functionallity to dump multiple tables with multiple -t table-name options. While digging in the source for pg_dump I see that many local static variables are not freed( with free(3)). Is this lazy programming because pg_dump is its own process where the kernel takes care of cleaning up, so you don't bother to do it for some of the variables? I'm malloc'ing some structs to build a list over tables which are marked for dumping. Shall I bother to free(3) them? - -- Andreas Joseph Krogh [EMAIL PROTECTED] Managing Director, Senior Software Developer OfficeNet AS - - Writing software is more fun than working. gpg public_key: http://dev.officenet.no/~andreak/public_key.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/cE2SUopImDh2gfQRAhOxAJ0Wr7s98ufN4BEckpVem/tFfekIwQCghS+3 8x/TV1Oqx++ywYDyOJxQSCU= =uKgq -END PGP SIGNATURE- ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] free(3)-ing variables in pg_dump
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 23 September 2003 16:25, Andrew Dunstan wrote: Andreas Joseph Krogh wrote: Hi. I'm trying to implement functionallity to dump multiple tables with multiple -t table-name options. excellent. While digging in the source for pg_dump I see that many local static variables are not freed( with free(3)). Is this lazy programming because pg_dump is its own process where the kernel takes care of cleaning up, so you don't bother to do it for some of the variables? I'm malloc'ing some structs to build a list over tables which are marked for dumping. Shall I bother to free(3) them? I don't think it's lazy, probably just a product of the programmer's awareness that little would be gained by it. Relying on the OS to clean up for you is perfectly valid in a shortlived program unless you get a major problem with memory leaks. I didn't mean lazy as in bad - I ment lazy as in just what you pointed out: little would be gained by it, so why bother. If it ain't broke, don't fix it would be my take. (If this is not the consensus I'm going to have some more work to do in the C port of initdb I'm working on, which is about one third done :-) :-) - -- Andreas Joseph Krogh [EMAIL PROTECTED] Managing Director, Senior Software Developer OfficeNet AS - - Writing software is more fun than working. gpg public_key: http://dev.officenet.no/~andreak/public_key.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/cF3DUopImDh2gfQRAtR4AJ499CK4QcGO9Dc0Wato46/wZMxZ/wCaApSP 463Z/DfsEBtUvQ50h/osKAc= =eEqD -END PGP SIGNATURE- ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] 3 digit ISO dates
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 15 September 2003 09:09, Christopher Kings-Lynne wrote: Hi, Are we going to address the fact that you can't enter 3 digit years without a leading 0? australia=# select '111-01-01'::date; ERROR: Bad date external representation '111-01-01' australia=# select '0111-01-01'::date; date 0111-01-01 (1 row) I can't see any reason why we shouldn't allow it??? Works here(7.4beta2): andreak=# select '111-01-01'::date; date - 0111-01-01 (1 row) andreak=# select version(); version - --- PostgreSQL 7.4beta2 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2.2 (Mandrake Linux 9.1 3.2.2-3mdk) (1 row) - -- Andreas Joseph Krogh [EMAIL PROTECTED] Managing Director, Senior Software Developer OfficeNet AS - - There are 10 kinds of people in the world, those that can do binary arithmetic and those that can't. gpg public_key: http://dev.officenet.no/~andreak/public_key.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/ZW3mUopImDh2gfQRAlNIAKCF62WbRGJSP1QwM+qJzUjBiSM3gQCbBM4N SmXAdFqCK+Wf6EVTw/W9buo= =+Hrc -END PGP SIGNATURE- ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
[HACKERS] on-disk format changes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi. Will there be any more on-disk format changes before 7.4 goes final which will require a dump-restore, or is that impossible to say? - -- Andreas Joseph Krogh [EMAIL PROTECTED] Managing Director, Senior Software Developer OfficeNet AS - - There are 10 kinds of people in the world, those that can do binary arithmetic and those that can't. gpg public_key: http://dev.officenet.no/~andreak/public_key.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/XHn1UopImDh2gfQRAlu7AJ42E+UX3LcjaZXMHo0KSz+clDXEAACfTHPX OSoPmCxxhN3OOXWEAh1e3SQ= =cc5z -END PGP SIGNATURE- ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] on-disk format changes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 08 September 2003 15:27, Bruno Wolff III wrote: On Mon, Sep 08, 2003 at 14:45:41 +0200, Andreas Joseph Krogh [EMAIL PROTECTED] wrote: Will there be any more on-disk format changes before 7.4 goes final which will require a dump-restore, or is that impossible to say? While it is impossible to say with 100% certainly, the developers generally try to avoid requiring initdbs after the first beta and especially after later betas. That's what I thought. I remember from the 7.3 beta-period that it broke between beta2 and beta3 or so and am wondering if the developers are aware of any known issues which might require an initdb after 7.4beta2. Lets hope not:-) - -- Andreas Joseph Krogh [EMAIL PROTECTED] Managing Director, Senior Software Developer OfficeNet AS - - There are 10 kinds of people in the world, those that can do binary arithmetic and those that can't. gpg public_key: http://dev.officenet.no/~andreak/public_key.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/XIM4UopImDh2gfQRAh6aAJ91T5oaU8X8Jac8Jq42qgyMv5NnCQCeORIa rr6pTlyA1HMNuEvdd+kzkzo= =93Bk -END PGP SIGNATURE- ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] tsearch2 for 7.3.X
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 21 July 2003 23:43, Oleg Bartunov wrote: On Mon, 21 Jul 2003, Andreas Joseph Krogh wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 21 July 2003 22:46, Bruce Momjian wrote: We don't normally issue new features in minor releases, but for a /contrib, we could consider it. --- Oleg Bartunov wrote: Hi there, seems we'll have 7.3.4 release. Is't worth to submit new tsearch2 module for this release ? People could play with new module without waiting 7.4 release. FWIW: I would very much appreciate a tsearch2 for 7.3 for testing without having to upgrade my db's to 7.4. One question tho, is it ready for production? It's the ranking support which I'm looking forward to. I think it's production quality. Actually, we use it in our projects with 7.3.3. You may read docs on tsearch2 home page http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/ I've read it, and it looks promissing, good work! - -- Andreas Joseph Krogh [EMAIL PROTECTED] gpg public_key: http://dev.officenet.no/~andreak/public_key.asc - - When there is no content, there is no crap. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE/HNvwUopImDh2gfQRAgvHAKCdmf2eNUvjsUx0Xw6ARNDoEEI9dQCeIvWg KdACyIa6jckNeu9MlHn4DLQ= =ge1g -END PGP SIGNATURE- ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] tsearch2 for 7.3.X
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 21 July 2003 22:46, Bruce Momjian wrote: We don't normally issue new features in minor releases, but for a /contrib, we could consider it. --- Oleg Bartunov wrote: Hi there, seems we'll have 7.3.4 release. Is't worth to submit new tsearch2 module for this release ? People could play with new module without waiting 7.4 release. FWIW: I would very much appreciate a tsearch2 for 7.3 for testing without having to upgrade my db's to 7.4. One question tho, is it ready for production? It's the ranking support which I'm looking forward to. - -- Andreas Joseph Krogh [EMAIL PROTECTED] gpg public_key: http://dev.officenet.no/~andreak/public_key.asc - - When there is no content, there is no crap. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE/HFYtUopImDh2gfQRAvj8AJ90UoHrSfumA0C4wUhkzh7bzfEN0gCfVsri NFWJfB/6ILRA6RsbMPUdcTQ= =HvZQ -END PGP SIGNATURE- ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
[HACKERS] Roadmap for 7.4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi. Does a roadmap exist for 7.4, so we know what features are to be implemented? This might be usefull for people evaluating PostgreSQL for their future projects. Should they wait for 7.4, or should they go with a commercial db which has the features they need. - -- Andreas Joseph Krogh [EMAIL PROTECTED] There will always be someone who agrees with you but is, inexplicably, a moron. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+IV9aUopImDh2gfQRAk3wAJ4sZ6eKU8pN2gDdSg6IKazRer4xZACgqyGT W7J9BijKn3SEDDvm/cT6XrQ= =Nn/Q -END PGP SIGNATURE- ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] [JDBC] Conversion between UNICODE and LATIN1 is not supported
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 19 December 2002 16:09, you wrote: Hello, Do you have other databases that work with UNICODE? You can check the encoding of all your databases with 'psql -l'. You can check if you can create any unicode databases with 'createdb -E UNICODE mytestdatabase'. I didn't use postgresql on solaris yet, so the following is just a guess: maybe you need to install additional solaris packages. For example to get tomcat/java working with utf-8/unicode/.. instead of plain ascii, we need at least the following on our systems: SUNWlocSystem Localization SUNWlocx System Localization (64-bit) SUNWeuluf UTF-8 L10N For Language Environment User Files SUNWeulux UTF-8 L10N For Language Environment User Files (64-bit) No, all our databases are LATIN1, it's the JDBC driver which want to set client_encoding = 'UNICODE'. I havn't tried to connect to a UNICODE (-E UNICODE) database with the JDBC driver. I now created a test database andreak with -E UNICODE Here is some output: [andreak@www2] ~$ uname -a SunOS www2.java.no 5.8 Generic_108528-16 sun4u sparc SUNW,Ultra-250 [andreak@www2] ~$ psql -l List of databases Name| Owner | Encoding - ---+--+--- andreak | andreak | UNICODE template0 | postgres | SQL_ASCII template1 | postgres | SQL_ASCII www | onp | LATIN1 (4 rows) [andreak@www2] ~$ psql andreak Welcome to psql 7.3, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help on internal slash commands \g or terminate with semicolon to execute query \q to quit andreak=# select version(); version - --- PostgreSQL 7.3 on sparc-sun-solaris2.8, compiled by GCC gcc (GCC) 3.2 (1 row) andreak=# show client_encoding ; client_encoding - - UNICODE (1 row) andreak=# set client_encoding = 'LATIN1'; ERROR: Conversion between LATIN1 and UNICODE is not supported andreak=# set client_encoding = 'UNICODE'; SET andreak=# \q [andreak@www2] ~$ psql www Welcome to psql 7.3, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help on internal slash commands \g or terminate with semicolon to execute query \q to quit www=# set client_encoding = 'LATIN1'; SET www=# set client_encoding = 'UNICODE'; ERROR: Conversion between UNICODE and LATIN1 is not supported www=# This works fine on Linux, I havn't tried to patch Solaris with l10n-stuff yet, but it would be nice to get some feedback and understand why this is happening and why I don't get a more descriptive error. For some reason none of the conversions work at all, except, of course, conversion between similar encodings like UNICODE-UNICODE. - -- Andreas Joseph Krogh [EMAIL PROTECTED] There will always be someone who agrees with you but is, inexplicably, a moron. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+AeQ4UopImDh2gfQRAuRvAKCbk4pyp7CbXiA4NGq8ntKpZ2IriwCeKcaC /pPGUgPzEuzDmIdX3shR8Ps= =EYP3 -END PGP SIGNATURE- ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
