Re: [HACKERS] pg_advisor schema proof of concept
Fabien COELHO wrote: Ok. A more precise question is: on the client side, whether PHP or anything else, can you take advantage of the information available and provide some usable somehow dedicated interface that would make it easy to access the available informations? What would help for that purpose? The current proposal is that the advices would be tables in a schema, so just by browsing the tables one can access advices. However, the tables contain the advice data, but explanations about what these advices mean are in another table. So maybe there is an interface job that would be welcome to show both the explanations and the data of interest for these explanations? Just like in psql \* shortcuts query about pg_tables to show informations. No problem, as long as referencing data is contained in the advice tables (i.e. referencing the 'offending' object), not just text so the advice can be shown as attribute of each object. Regards, Andreas ---(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] A student research project on triggers
Grace Mou wrote: I'm currently working on a student research project that is supervised by a professor from my university. This project duration is 2 semesters. The topic is to implement the two missing SQL3 standard triggers functionalities in Postgresql, ¡®triggers on columns¡¯ and ¡®referencing old or new values alias list¡¯ in trigger definition. A short brief of me:I am a Computer Science master student in the 5th semester in Ottawa U, Canada. I have 10 years experiences in C/C++ programming; I am also working as a Unix system administrator for a large semiconductor Company. I would like to get some help about where to start, any ideas, suggestions or hints are appreciated. Mark [EMAIL PROTECTED] Please read the developer's FAQ first, and see the rest of the developer's page. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(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] Timeline for 7.4.3?
Tom Lane wrote: Joshua D. Drake [EMAIL PROTECTED] writes: We have many machines that run Solaris. I know that there are patches out there for some of the bugs in 7.4.2 for Solaris but I was wondering what the timeline for an official 7.4.3 was? Don't hold your breath ... 7.4.2 was only a couple weeks ago, and there are no critical bugs in the CVS logs at this point. The only post-7.4.2 Solaris fixes I can think of are for threaded builds. Do you use those? If so, you can grab CVS REL7_4_STABLE and see how that works for you. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[HACKERS] md5 function
can you create second md5 function like TEXT md5(TEXT string, VARCHAR salt); ? , This is using in shadow passwords and give more combination of this same password. thanks, bye ivan ---(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] PostgreSQL block size vs. LVM2 stripe width
Mark, how often did you run your tests? Are the results reproduceable? On Fri, 26 Mar 2004 14:00:01 -0800 (PST), [EMAIL PROTECTED] wrote: Linux-2.6.3, LVM2 Stripe Width (going across) PostgreSQL BLCKSZ (going down)16 KB 32 KB 64 KB 128 KB 256 KB 512 KB 2 KB261726562652266426672642 4 KB439344864577455745114448 8 KB433744234471457641113642 16 KB 441244954532453629852312 32 KB 370537843886392529362362 Unless someone can present at least an idea of a theory why a BLCKSZ of 8 KB is at a local minimum (1 or 2% below the neighbouring values) for stripe widths up to 64 KB I'm not sure whether we can trust these numbers. Before I hit the send button, I did a quick check of the link you provided. The links in the table contain the following test numbers: 16 KB 32 KB 64 KB 128 KB 256 KB 512 KB 2 KB 72 71 70 69 66 65 4 KB 64 63 62 61 60 58 8 KB 54 53 52 51 50 49 16 KB79 78 77 76 75 74 32 KB86 85 84 83 82 80 Does this mean that you first ran all test with 8 KB, then with 4, 2, 16 and 32 KB BLCKSZ? If so, I suspect that you are measuring the effects of something different. Servus Manfred ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] md5 function
ivan wrote: can you create second md5 function like TEXT md5(TEXT string, VARCHAR salt); ? , This is using in shadow passwords and give more combination of this same password. Yes, please see src/contrib/pgcrypto. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[HACKERS] default enconding
Hi, I have found what I thing is a quite annoying behaviour of Postgres (psql). When you type (and ask for complation) for some string that has some characters not in the ASCII encoding it requires a double quote on it, however if you don't put those double quotes around it, you can still execute the query. So what about changing the behaviour to either don't accept characters with the 8 bit set or accept by default strings in the iso-8859-1 encoding instead of ASCII endoding by default. Regards, Manuel. ---(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] default enconding
Manuel Sugawara [EMAIL PROTECTED] writes: Hi, I have found what I thing is a quite annoying behaviour of Postgres (psql). When you type (and ask for complation) for some string that has some characters not in the ASCII encoding it requires a double quote on it, however if you don't put those double quotes around it, you can still execute the query. ... in other words, it doesn't require the double quotes. I don't see the value of being more restrictive. Why is this annoying? regards, tom lane ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] default enconding
Tom Lane [EMAIL PROTECTED] writes: ... in other words, it doesn't require the double quotes. I don't see the value of being more restrictive. Why is this annoying? Note also that using iso-8859-1 is not more restrictive, but just the opposite. Using iso-8859-1 will be useful also for English users since some words in use in the English language use characters not in the ASCII encoding, resumé for instance. Regards, Manuel. ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] default enconding
Tom Lane [EMAIL PROTECTED] writes: Manuel Sugawara [EMAIL PROTECTED] writes: Hi, I have found what I thing is a quite annoying behaviour of Postgres (psql). When you type (and ask for complation) for some string that has some characters not in the ASCII encoding it requires a double quote on it, however if you don't put those double quotes around it, you can still execute the query. ... in other words, it doesn't require the double quotes. I don't see the value of being more restrictive. Why is this annoying? It's because you can't complete without the double quote, so, select something.fotab doesn't complete if you have only foó as the only completion whereas select something .fo does. Regards, Manuel. ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] default enconding
Hi, I have found what I thing is a quite annoying behaviour of Postgres (psql). When you type (and ask for complation) for some string that has some characters not in the ASCII encoding it requires a double quote on it, however if you don't put those double quotes around it, you can still execute the query. So what about changing the behaviour to either don't accept characters with the 8 bit set or accept by default strings in the iso-8859-1 encoding instead of ASCII endoding by default. Apparently regarding everything ISO-8859-1 is not correct:-) Probably we need to make quote_indet() a little bit smarter so that it should quote input text only when it includes ASCII capital letters and any other non delimter-appropreate letters except 8 bit characters. BTW, currently tab completion is not working for multibyte encoding(including UTF-8, I guess) because it's broken in that it's not multibyte ware. I think we need to fix that as well. -- Tatsuo Ishii ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] default enconding
Tatsuo Ishii [EMAIL PROTECTED] writes: I think we need to fix that as well. I do agreee, however, we have to start somewhere. Regards, Manuel. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
