[HACKERS] EuroOSCON
Is anybody at all from the hackers community going to be at EuroOSCON this year? (or active users, for that matter) If so, please contact me off-list. Thanks //Magnus ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] [COMMITTERS] pgsql: Second try committing the path changes.
On Tue, Aug 29, 2006 at 03:35:14PM -0500, Jaime Casanova wrote: Ah. So this would have caused a bunch of problems in compiling src/interfaces/ecpg/test/connect/test1.pgc??? Not the compilation errors I would think. i'm seeing this error when compiling HEAD (updated at ago 29 15:16) ... This looks like you're using an old version of the parser. preproc.y was changed to handle empty database names and the the error you report is due to an empty db name. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL! ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[HACKERS] Status on Fedora Core Extras packaging
Hello, Yesterday night, I was approved (sponsored) for Fedora Core packaging (please note that this is not something financial). For the beginning, I officially submitted python-psycopg2 to FC6. More are on the way; like pgpool, Slony-I, pgadmin3-adminpacks, phpPgAdmin, postgresql_autodoc, pgfouine. Also they are in the queue for FC5. I'm waiting for approval for them. More will be in FC Extras. Please let me know that if you want to see any PostgreSQL related software in the repository. I do have time to package all related stuff. Regards, -- The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564 PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/ signature.asc Description: This is a digitally signed message part
Re: [HACKERS] [PATCHES] updated patch for selecting large results
On Tue, 2006-08-29 at 18:31 -0400, Tom Lane wrote: [EMAIL PROTECTED] writes: here comes the latest version (version 7) of the patch to handle large result sets with psql. As previously discussed, a cursor is used for SELECT queries when \set FETCH_COUNT some_value 0 Applied with revisions ... I didn't like the fact that the code was restricted to handle only unaligned output format, so I fixed print.c to be able to deal with emitting output in sections. This is not ideal for aligned output mode, because we compute column widths separately for each FETCH group, but all the other output modes work nicely. I also did a little hacking to make \timing and pager output work as expected. regards, tom lane Cool! I specially like that as a side effect of your work for applying this, psql is faster now. Thanks to all people that helped with this (lots...:) Bye, Chris. -- Chris Mair http://www.1006.org ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] [PATCHES] Backend SSL configuration enhancement
Victor B. Wagner [EMAIL PROTECTED] writes: This patch adds two new configuration diretives to postgresql.conf file 1. ssl_ciphers - allows server administrator to specify set of SSL ciphersuites which can be used by clients to connect the server. 2. ssl_engine - allows to specify loadable crypto engin (i.e. hardware crypto accelerator support) to use. Why are either of these useful? What are the compatibility implications of changing them? Does the addition of the engine-load code break compatibility with older OpenSSL releases? regards, tom lane ---(end of broadcast)--- TIP 1: 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] [PATCHES] Backend SSL configuration enhancement
Tom Lane wrote: Victor B. Wagner [EMAIL PROTECTED] writes: This patch adds two new configuration diretives to postgresql.conf file 1. ssl_ciphers - allows server administrator to specify set of SSL ciphersuites which can be used by clients to connect the server. 2. ssl_engine - allows to specify loadable crypto engin (i.e. hardware crypto accelerator support) to use. Why are either of these useful? What are the compatibility implications of changing them? Does the addition of the engine-load code break compatibility with older OpenSSL releases? Is it just me, or are we seeing more patches lately that have been undiscussed? cheers andrew ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] stats test on Windows is now failing repeatably?
ITAGAKI Takahiro [EMAIL PROTECTED] writes: I tested HEAD on Windows and saw some Windows-specific logs. LOG: Windows fopen(base/16384/pg_internal.init,rb) failed: code 2, errno 2 LOG: Windows fopen(global/pgstat.stat,rb) failed: code 32, errno 13 The code 2 means ERROR_FILE_NOT_FOUND, The system cannot find the file specified. and the code 32 means ERROR_SHARING_VIOLATION, The process cannot access the file because it is being used by another process. The first of those is probably normal operation --- we remove pg_internal.init whenever it is out-of-date. The second is bad though. We use the tmpfile-and-rename trick on both pg_internal.init and pgstat.stat. Are there any incompatible behavior in the trick between POSIX and Windows? It looks to me like we have implemented Windows' FILE_SHARE_DELETE flag for open() calls but not for fopen(). Isn't this a problem? We do use fopen() for stuff like pgstat.stat. regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [HACKERS] Coding style for emacs
Bruce Momjian wrote: Andrew Dunstan wrote: I will try to draw all this together today or tomorrow. It's not only the FAQ that should be patched - the docs and the FAQ should agree with each other. Right. In fact, this info arguably belongs in one place only. Which should it be? Uh, if you put it in the docs, I can reference it from the FAQ, but not the other way around, so I think the documentation is best. Looking at this further, I am wondering if it would not be better to put sample .emacs and .vimrc files in the source (in, say, src.tools). The docs/FAQ would just say that we use BSD style with tab space 4 and refer to the sample files. thoughts? cheers andrew ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [HACKERS] Autovacuum on by default?
On Tue, Aug 29, 2006 at 09:23:53PM -0700, Josh Berkus wrote: Peter, OK, it seems that while everyone wants autovacuum be more aggressive by default, no one has any good data to support one setting or another. I so I suggest that we just cut scale factor and base threshold in half right now (so it'd be 0.2, 0.1, 500, 250) and see about a better-researched setting for the next release. I'd recommend actually 0.4 and 0.2 and 200 and 100. I think that 20% and 10% are too aggresive. 0.4 and 0.2 are what I've been using in production on many machines. On the other hand, I think that the thresholds are much too high -- that means that many small tables may never get vacuumed at all, even after 100% row replacement. Do you think .2 and .1 (or even .08 and .04, as suggested by the default page fill percentage) are too aggressive *on small systems*? IMO, these defaults are meant more for less experienced folks, which are much more likely to be running a smaller database than a large one. FWIW, I've been using .2 and .1 (as well as cutting the thresholds down; typically to between 200 and 400 and 100 and 200) without issue, though I did tweak the delay costs at one customer. I'll admit, however, that I don't have test data to support this. Unfortunately we never got to good Autovac tests on the STP before it went down. -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.comwork: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] stats test on Windows is now failing repeatably?
Magnus Hagander [EMAIL PROTECTED] writes: It looks to me like we have implemented Windows' FILE_SHARE_DELETE flag for open() calls but not for fopen(). Isn't this a problem? We do use fopen() for stuff like pgstat.stat. That definitely sounds like a problem, there is no reason why the issue shouldn't occur for fopen(). Do you want to work up a patch for that based on open(), or do you want me to take a look at it? It looks straightforward to apply our reimplemented pgwin32_open() followed by fdopen(), but since I don't have a Windows build environment I couldn't test the patch. Please take a look at it. regards, tom lane ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] TODO Request
On Tue, Aug 29, 2006 at 03:53:57PM -0700, Joshua D. Drake wrote: Hello, Can we get: Multiple table indexes (for uniqueness across partitions for example) Before any of the below happen, I think it'd be good to get a cleaner way to define partitions; one that didn't involve manually messing with constraints, etc. Auto creations of partitions That would be nice, though if we had a built-in job facility of some kind it wouldn't be needed for time-based partitioning. Hash partitioning Key partitioning Sub partitioning Is there anything stopping those from being done right now? The only thing I can think of that we're missing is an optimization where a partition with a single key doesn't contain that key's data. Currently, this can be done with UNION VIEW partitioning, but perhaps there's some more clever way to do it in the inheritance case. -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.comwork: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] Coding style for emacs
Andrew Dunstan [EMAIL PROTECTED] writes: Looking at this further, I am wondering if it would not be better to put sample .emacs and .vimrc files in the source (in, say, src.tools). Seems reasonable. I was about to say what if they're just looking at the docs and don't have a source tree? ... but anyone editing the code has got a copy of the source tree ... regards, tom lane ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[HACKERS] I need your help!!
Hi!! I hope you are not too busy. The thing is that i need to connect my pc which is on windows XP and the server is on linux with postgres. The question is? how do I connect my windows machine to the server with postgres? What do I have to do?, put it in steps please!!! thanks you guys are great!!! _ Prodigy/MSN Search. Todo lo que buscas ahora más rapido http://search.t1msn.com.mx/ ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] stats test on Windows is now failing repeatably?
The code 2 means ERROR_FILE_NOT_FOUND, The system cannot find the file specified. and the code 32 means ERROR_SHARING_VIOLATION, The process cannot access the file because it is being used by another process. The first of those is probably normal operation --- we remove pg_internal.init whenever it is out-of-date. The second is bad though. We use the tmpfile-and-rename trick on both pg_internal.init and pgstat.stat. Are there any incompatible behavior in the trick between POSIX and Windows? It looks to me like we have implemented Windows' FILE_SHARE_DELETE flag for open() calls but not for fopen(). Isn't this a problem? We do use fopen() for stuff like pgstat.stat. That definitely sounds like a problem, there is no reason why the issue shouldn't occur for fopen(). Do you want to work up a patch for that based on open(), or do you want me to take a look at it? //Magnus ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [HACKERS] I need your help!!
mario tovilla wrote: Hi!! I hope you are not too busy. The thing is that i need to connect my pc which is on windows XP and the server is on linux with postgres. The question is? how do I connect my windows machine to the server with postgres? What do I have to do?, put it in steps please!!! First thing, you ask on the right list, namely pgsql-general. This list is for development discussion, not general help. cheers andrew ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] I need your help!!
Hi, if you want to use a gui-tool try pgadmin3 http://www.postgresql.org/ftp/pgadmin3/release/v1.4.3/win32/ if you want to access your db from a generic client tool like access try the pgsqlodbc-driver official page http://pgfoundry.org/projects/psqlodbc/ latest snapshots http://www.geocities.jp/inocchichichi/psqlodbc/index.html HINT : This is the list for pgsql-development, better try the general-list pgsql-general@postgresql.org here you can choose the right list to subscribe : http://www.postgresql.org/community/lists/subscribe At available lists choose general or novice or read the faq Best regards Hakan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of mario tovilla Sent: Wednesday, August 30, 2006 12:41 AM To: pgsql-hackers@postgresql.org Subject: [HACKERS] I need your help!! Hi!! I hope you are not too busy. The thing is that i need to connect my pc which is on windows XP and the server is on linux with postgres. The question is? how do I connect my windows machine to the server with postgres? What do I have to do?, put it in steps please!!! thanks you guys are great!!! _ Prodigy/MSN Search. Todo lo que buscas ahora más rapido http://search.t1msn.com.mx/ ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] [PATCHES] Updatable views
Bernd Helmle [EMAIL PROTECTED] writes: [ latest views patch ] This is the first time I've actually looked at this patch, and I am dismayed. viewUpdate.c looks like nothing so much as a large program with a small program struggling to get out. What is all the stuff about handling multiple base rels? SQL92, at least, does not say that a join is updatable, and AFAICT this patch is rejecting that too ... though it's hard to tell with the conditions for allowing the join to be updatable scattered through a lot of different functions. And some of the code seems to be expecting multiple implicit rules and other parts not. I get the impression that a lot of this code is left over from a more ambitious first draft and ought to be removed in the name of readability/maintainability. I'm unclear as to why you've got DO INSTEAD NOTHING rules in there --- the spec says that a WITH CHECK OPTION violation results in an error, not in nothing happening, so it doesn't seem to me that we should need any NOTHING rules to implement the spec. It would probably help if there were some header documentation that explained exactly how the module intends to transform a SELECT to create the various action rules. The pg_dump changes seem pretty odd too. Why wouldn't you just ignore implicit rules during a dump, expecting the system to regenerate them when the view is reloaded? regards, tom lane ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] [COMMITTERS] pgsql: Second try committing the path changes.
On 8/30/06, Michael Meskes [EMAIL PROTECTED] wrote: On Tue, Aug 29, 2006 at 03:35:14PM -0500, Jaime Casanova wrote: i'm seeing this error when compiling HEAD (updated at ago 29 15:16) ... This looks like you're using an old version of the parser. preproc.y was changed to handle empty database names and the the error you report is due to an empty db name. seems, you are right... i had downloaded the entire CVS again and now all is working fine -- regards, Jaime Casanova Programming today is a race between software engineers striving to build bigger and better idiot-proof programs and the universe trying to produce bigger and better idiots. So far, the universe is winning. Richard Cook ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [HACKERS] [COMMITTERS] pgsql: Second try committing the path changes.
[EMAIL PROTECTED] (Michael Meskes) writes: On Tue, Aug 29, 2006 at 03:35:14PM -0500, Jaime Casanova wrote: Ah. So this would have caused a bunch of problems in compiling src/interfaces/ecpg/test/connect/test1.pgc??? Not the compilation errors I would think. i'm seeing this error when compiling HEAD (updated at ago 29 15:16) ... This looks like you're using an old version of the parser. preproc.y was changed to handle empty database names and the the error you report is due to an empty db name. I think the problem is that the latest version of preproc.c isn't based on that version of preproc.y (or perhaps similarly with pgc.l/pgc.c). If I touch preproc.y and pgc.l, the .c files get regenerated, and all is well. If I don't, they get left alone, and I see compilation errors. It seems to me you need to rebuild the C files and commit them. -- select 'cbbrowne' || '@' || 'ntlug.org'; http://www3.sympatico.ca/cbbrowne/lsf.html When I die, I'd like to go peacefully in my sleep like my grandfather, not screaming in terror like his passengers... ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] [COMMITTERS] pgsql: Second try committing the path changes.
Chris Browne [EMAIL PROTECTED] writes: If I touch preproc.y and pgc.l, the .c files get regenerated, and all is well. If I don't, they get left alone, and I see compilation errors. It seems to me you need to rebuild the C files and commit them. No, because those derived files are not in CVS at all. What you are describing sounds to me like a clock skew problem. Is your machine's system clock showing the correct date? regards, tom lane ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] stats test on Windows is now failing repeatably?
It looks to me like we have implemented Windows' FILE_SHARE_DELETE flag for open() calls but not for fopen(). Isn't this a problem? We do use fopen() for stuff like pgstat.stat. That definitely sounds like a problem, there is no reason why the issue shouldn't occur for fopen(). Do you want to work up a patch for that based on open(), or do you want me to take a look at it? It looks straightforward to apply our reimplemented pgwin32_open() followed by fdopen(), but since I don't have a Windows build environment I couldn't test the patch. Please take a look at it. I think this is what we want. It passes regression tests on my machine. I never managed to reproduce the original problem on this machine, so don't know if it solves the problem, but I don't think it makes it worse :-) //Magnus win32_fopen.diff Description: win32_fopen.diff ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] stats test on Windows is now failing repeatably?
Magnus Hagander [EMAIL PROTECTED] writes: It looks straightforward to apply our reimplemented pgwin32_open() followed by fdopen(), but since I don't have a Windows build environment I couldn't test the patch. Please take a look at it. I think this is what we want. It passes regression tests on my machine. I never managed to reproduce the original problem on this machine, so don't know if it solves the problem, but I don't think it makes it worse :-) Applied, we'll see what happens ... regards, tom lane ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] [PATCHES] Updatable views
On Wed, Aug 30, 2006 at 12:01:25PM -0400, Tom Lane wrote: Bernd Helmle [EMAIL PROTECTED] writes: [ latest views patch ] This is the first time I've actually looked at this patch, and I am dismayed. viewUpdate.c looks like nothing so much as a large program with a small program struggling to get out. What is all the stuff about handling multiple base rels? SQL92, at least, does not say that a join is updatable, and AFAICT this patch is rejecting that too ... though it's hard to tell with the conditions for allowing the join to be updatable scattered through a lot of different functions. And some of the code seems to be expecting multiple implicit rules and other parts not. I get the impression that a lot of this code is left over from a more ambitious first draft and ought to be removed in the name of readability/maintainability. If that code is on the right path to allowing things like updates to the many side of a join then it would be worth adding comments to that effect. Or maybe a comment referencing whatever version of the file the code was yanked out of. -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.comwork: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] pgcrypto deprecated functions?
Michael Fuhr wrote: In README.pgcrypto, Section 2.3 Deprecated functions says that digest_exists(), hmac_exists(), and cipher_exists() are planned to be removed in PostgreSQL 8.2. Those functions still exist -- should they be removed or does that section need updating? Marko, any comment on this pgcrypto item? -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Status on Fedora Core Extras packaging
On Wed, Aug 30, 2006 at 12:12:30 +0300, Devrim GUNDUZ [EMAIL PROTECTED] wrote: More will be in FC Extras. Please let me know that if you want to see any PostgreSQL related software in the repository. I do have time to package all related stuff. Do you think you could have a way to store target coordinates and access times in a Postgres database for people who want to use Fedora's Orbital Laser? ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] Coding style for emacs
On Wed, Aug 30, 2006 at 11:06:01AM -0400, Andrew Dunstan wrote: Bruce Momjian wrote: Andrew Dunstan wrote: I will try to draw all this together today or tomorrow. It's not only the FAQ that should be patched - the docs and the FAQ should agree with each other. Right. In fact, this info arguably belongs in one place only. Which should it be? Uh, if you put it in the docs, I can reference it from the FAQ, but not the other way around, so I think the documentation is best. Looking at this further, I am wondering if it would not be better to put sample .emacs and .vimrc files in the source (in, say, src.tools). The docs/FAQ would just say that we use BSD style with tab space 4 and refer to the sample files. thoughts? If we put them in a place that's visible before you get the source, we can help people use the settings globally :) Cheers, D -- David Fetter [EMAIL PROTECTED] http://fetter.org/ phone: +1 415 235 3778AIM: dfetter666 Skype: davidfetter Remember to vote! ---(end of broadcast)--- TIP 1: 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] [PATCHES] Backend SSL configuration enhancement
Victor B. Wagner wrote: First one is useful if for some reason some ciphers supported by OpenSSL is not permitted to use in the particular network, or if there is need to use ciphersuites which are not included into default ciphersuite list, now compiled into PostgreSQL. Do you have specific examples where that might be the case? Second one can be used for taking cryptography load from server into special hardware chip, which can be useful for loaded servers. Also, upcoming OpenSSL 0.9.9 allows to add entirely new cryptographic algorithms via engines, so engine support allows to use algorithms, ISTM that that should be in a system-wide OpenSSL configuration, not to be hacked into each SSL-using application separately. Is that possible? -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Coding style for emacs
David Fetter wrote: Looking at this further, I am wondering if it would not be better to put sample .emacs and .vimrc files in the source (in, say, src.tools). The docs/FAQ would just say that we use BSD style with tab space 4 and refer to the sample files. thoughts? If we put them in a place that's visible before you get the source, we can help people use the settings globally :) The likely level of our influence on someone who hasn't used the settings and isn't editing our source code is approximately equal to the influence of Pluto's gravitational field on your mood when you got out of bed this morning. cheers andrew ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] Coding style for emacs
Andrew Dunstan wrote: David Fetter wrote: If we put them in a place that's visible before you get the source, we can help people use the settings globally :) The likely level of our influence on someone who hasn't used the settings and isn't editing our source code is approximately equal to the influence of Pluto's gravitational field on your mood when you got out of bed this morning. I always wondered what affected his mood when he got out of bed this morning. Now I know! It's amazing the things you can learn by lurking here... :-) -- Kevin Brown [EMAIL PROTECTED] ---(end of broadcast)--- TIP 1: 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: [PATCHES] [HACKERS] Performance testing of COPY (SELECT) TO
=?iso-8859-2?Q?B=F6sz=F6rm=E9nyi_Zolt=E1n?= [EMAIL PROTECTED] writes: as per your suggestion, the COPY view TO support was cut and a hint was added. Please, review. Committed after some refactoring to avoid code duplication. Unfortunately, in a moment of pure brain fade, I looked at the wrong item in my inbox and wrote Bernd Helmle's name instead of yours in the commit message :-(. My sincere apologies. Bruce, would you make a note to be sure the right person gets credit in the release notes? regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[HACKERS] GIN FailedAssertions on Itanium2 with Intel compiler
Hello -hackers, I see a make check failures on Itanium2 platform with Intel Compiler with CVS HEAD. A failure is coming for GIN. The problem is coming at the assertion at ginbulk.c:62 TRAP: FailedAssertion(!(res != 0), File: ginbulk.c, Line: 62) during the index creation from the regr. tests CREATE INDEX ii on array_index_op_test using gin(i); The backtraces before the assertion (unfortunately from intel debugger...): (idb) bt #0 0x4014d370 in ginChooseElem (accum=0x3, heapptr=0x182, entries=0x120012, nentry=16384, low=2, high=16, offset=8192) at ginbulk.c:62 #1 0x4014cd00 in ginChooseElem (accum=0x3, heapptr=0x182, entries=0x120012, nentry=16384, low=2, high=16, offset=8192) at ginbulk.c:168 #2 0x4014c790 in ginInsertRecordBA (accum=0x3, heapptr=0x182, entries=0x120012, nentry=16384) at ginbulk.c:192 #3 0x40123380 in ginBuildCallback (index=0x3, htup=0x182, values=0x120012, isnull=0x4000 no value, tupleIsAlive=2 '\002', state=0x180010) at gininsert.c:203 #4 0x40174ee0 in IndexBuildHeapScan (heapRelation=0x3, indexRelation=0x182, indexInfo=0x120012, callback=0x4000, callback_state=0x182) at index.c:1534 #5 0x40124ea0 in ginbuild (fcinfo=0x3) at gininsert.c:311 #6 0x406eaf00 in OidFunctionCall3 (functionId=3, arg1=1649267441666, arg2=77309411346, arg3=16384) at fmgr.c:1460 #7 0x40177390 in reindex_relation (relid=3, toast_too=2 '\002') at index.c:1282 #8 0x40172700 in index_create (heapRelationId=3, indexRelationName=0x182 no value, indexRelationId=18, indexInfo=0x4000, accessMethodObjectId=2, tableSpaceId=16, classObjectId=0x2000, reloptions=1649267441666, isprimary=0 '\000', isconstraint=0 '\000', allow_system_table_mods=0 '\000', skip_build=0 '\000', concurrent=0 '\000') at index.c:782 ---Type return to continue, or q return to quit--- #9 0x40270df0 in DefineIndex (heapRelation=0x3, indexRelationName=0x182 no value, indexRelationId=18, accessMethodName=0x4000 no value, tableSpaceName=0x182 no value, attributeList=0x180010, predicate=0x2000, rangetable=0x182, options=0x0, unique=0 '\000', primary=0 '\000', isconstraint=0 '\000', is_alter_table=0 '\000', check_rights=1 '\001', skip_build=0 '\000', quiet=0 '\000', concurrent=0 '\000') at indexcmds.c:440 #10 0x4051b3b0 in ProcessUtility (parsetree=0x3, params=0x182, dest=0x120012, completionTag=0x4000 no value) at utility.c:789 #11 0x40518100 in PortalRunMulti (portal=0x3, dest=0x182, altdest=0x120012, completionTag=0x4000 no value) at pquery.c:1062 #12 0x40516f90 in PortalRun (portal=0x3, count=1649267441666, dest=0x120012, altdest=0x4000, completionTag=0x182 no value) at pquery.c:700 #13 0x4050e770 in exec_simple_query (query_string=0x3 no value) at postgres.c:1003 #14 0x4050bc20 in PostgresMain (argc=3, argv=0x182, username=0x120012 no value) at postgres.c:3263 #15 0x4045fc20 in BackendRun (port=0x3) at postmaster.c:2848 #16 0x4045ea80 in ServerLoop () at postmaster.c:2485 #17 0x4045c310 in PostmasterMain (argc=3, argv=0x182) at postmaster.c:950 #18 0x4035a0b0 in main (argc=3, argv=0x182) at main.c:187 (idb) bt full #0 0x4014d370 in ginChooseElem (accum=0x3, heapptr=0x182, entries=0x120012, nentry=16384, low=2, high=16, offset=8192) at ginbulk.c:62 middle=Info: symbol middle is defined but not allocated (optimized away) no value pos=Info: symbol pos is defined but not allocated (optimized away) no value #1 0x4014cd00 in ginChooseElem (accum=0x3, heapptr=0x182, entries=0x120012, nentry=16384, low=2, high=16, offset=8192) at ginbulk.c:168 middle=Info: symbol middle is defined but not allocated (optimized away) no value pos=Info: symbol pos is defined but not allocated (optimized away) no value #2 0x4014c790 in ginInsertRecordBA (accum=0x3, heapptr=0x182, entries=0x120012, nentry=16384) at ginbulk.c:192 i=Info: symbol i is defined but not allocated (optimized away) no value nbit=Info: symbol nbit is defined but not allocated (optimized away) no value offset=Info: symbol offset is defined but not allocated (optimized away) no value #3 0x40123380 in ginBuildCallback (index=0x3, htup=0x182, values=0x120012, isnull=0x4000 no value, tupleIsAlive=2 '\002', state=0x180010) at gininsert.c:203 ---Type return to continue, or q return to quit--- buildstate=Info: symbol buildstate is defined but not allocated (optimized away) no value oldCtx=Info: symbol oldCtx is defined but not allocated (optimized away) no value #4 0x40174ee0 in IndexBuildHeapScan (heapRelation=0x3, indexRelation=0x182, indexInfo=0x120012,
Re: [HACKERS] Coding style for emacs
On Wed, Aug 30, 2006 at 06:28:06PM -0400, Andrew Dunstan wrote: David Fetter wrote: thoughts? If we put them in a place that's visible before you get the source, we can help people use the settings globally :) The likely level of our influence on someone who hasn't used the settings and isn't editing our source code is approximately equal to the influence of Pluto's gravitational field on your mood when you got out of bed this morning. I want to believe! ;) Cheers, D -- David Fetter [EMAIL PROTECTED] http://fetter.org/ phone: +1 415 235 3778AIM: dfetter666 Skype: davidfetter Remember to vote! ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [HACKERS] Coding style for emacs
David Fetter wrote: On Wed, Aug 30, 2006 at 06:28:06PM -0400, Andrew Dunstan wrote: David Fetter wrote: thoughts? If we put them in a place that's visible before you get the source, we can help people use the settings globally :) The likely level of our influence on someone who hasn't used the settings and isn't editing our source code is approximately equal to the influence of Pluto's gravitational field on your mood when you got out of bed this morning. I want to believe! ;) You will pull Joe from my cold dead hands! Cheers, D -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ ---(end of broadcast)--- TIP 1: 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: [PATCHES] [HACKERS] Performance testing of COPY (SELECT)
Tom Lane wrote: =?iso-8859-2?Q?B=F6sz=F6rm=E9nyi_Zolt=E1n?= [EMAIL PROTECTED] writes: as per your suggestion, the COPY view TO support was cut and a hint was added. Please, review. Committed after some refactoring to avoid code duplication. Unfortunately, in a moment of pure brain fade, I looked at the wrong item in my inbox and wrote Bernd Helmle's name instead of yours in the commit message :-(. My sincere apologies. Bruce, would you make a note to be sure the right person gets credit in the release notes? Fixed with new commit message to copy.c. -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 1: 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] Coding style for emacs
Andrew Dunstan wrote: Looking at this further, I am wondering if it would not be better to put sample .emacs and .vimrc files in the source (in, say, src.tools). What does people use in .vimrc? Mine has simply this: : set cinoptions=(0 : set tabstop=4 : set shiftwidth=4 wrapped in a :if match(getcwd(), /home/alvherre/Code/CVS/pgsql) == 0 ... :endif of course. I find it to be all I need to get the style Postgres uses. (On the other hand, default cinoptions may be different on other versions of Vim) -- Alvaro Herrerahttp://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[HACKERS] Is this getting through?
Are my mails getting through? Did anyone see my mail about the GIN docs? ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] stats test on Windows is now failing repeatably?
Magnus Hagander [EMAIL PROTECTED] wrote: FILE_SHARE_DELETE I think this is what we want. It passes regression tests on my machine. I never managed to reproduce the original problem on this machine, so don't know if it solves the problem, but I don't think it makes it worse :-) It seems to work very well! I ran the same workload on the HEAD, and I did not see any pgstat.stat related logs now. Regards, --- ITAGAKI Takahiro NTT Open Source Software Center ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] Is this getting through?
Christopher Kings-Lynne wrote: Are my mails getting through? Did anyone see my mail about the GIN docs? I got it. Joshua D. Drake ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [PATCHES] [HACKERS] Performance testing of COPY (SELECT) TO
Thanks!!! Tom Lane írta: =?iso-8859-2?Q?B=F6sz=F6rm=E9nyi_Zolt=E1n?= [EMAIL PROTECTED] writes: as per your suggestion, the COPY view TO support was cut and a hint was added. Please, review. Committed after some refactoring to avoid code duplication. Unfortunately, in a moment of pure brain fade, I looked at the wrong item in my inbox and wrote Bernd Helmle's name instead of yours in the commit message :-(. My sincere apologies. Bruce, would you make a note to be sure the right person gets credit in the release notes? regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Is this getting through?
I store it, thank you. But we want to add something before commiting. Christopher Kings-Lynne wrote: Are my mails getting through? Did anyone see my mail about the GIN docs? ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings -- Teodor Sigaev E-mail: [EMAIL PROTECTED] WWW: http://www.sigaev.ru/ ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
