[PERFORM] unsubscribe
---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[PERFORM] UNSUBSCRIBE
- Original Message - From: Jim C. Nasby [EMAIL PROTECTED] To: Bob Dusek [EMAIL PROTECTED] Cc: pgsql-performance@postgresql.org Sent: Wednesday, January 10, 2007 2:01 PM Subject: Re: [PERFORM] performance implications of binary placement Are you 100% certain that both builds are using all the same libraries? And to be an apples-apples comparison, you really need to ensure that the datadir is on the same filesystem in both cases (that's the first thing I'd check). Also, that pg_index... error sounds like the second build has been corrupted. On Tue, Dec 26, 2006 at 03:37:47PM -0500, Bob Dusek wrote: Hello all, I've been running performance tests on various incantations of Postgres on/off for a month or so. And, I've just come across some unexpected results. When I start my Postgres build as such: # (Scenario 1) ./configure --prefix=/usr --libdir=/usr/lib --bindir=/usr/bin --includedir=/usr/include/pgsql --datadir=/usr/share/postgresql --mandir=/usr/share/man --with-docdir=/usr/share/doc/packages --disable-rpath --enable-thread-safety --enable-integer-datetimes --without-python --without-perl --without-tcl --without-tk It performs significantly worse than when I start my build like this: # (Scenario 2) ./configure --disable-rpath --enable-thread-safety --enable-integer-datetimes --without-python --without-perl --without-tcl --without-tk Note: the only differences are that Scenario 1 includes these options: --prefix=/usr --libdir=/usr/lib --bindir=/usr/bin --includedir=/usr/include/pgsql --datadir=/usr/share/postgresql --mandir=/usr/share/man --with-docdir=/usr/share/doc/packages And, to be clear, Scenario 1 performs worse than Scenario 2. Simple insert statements are taking significantly longer. I did not expect to see a performance hit with these options, especially since /usr/ on the test machine is mounted as its own partition, and in both cases, all of the binaries, include files, etc. are in that partition. Has anyone seen this before? Are hard drive mechanics the only thing in play here? The only difference I'm seeing in logging between the two versions is that Scenario 2 has several of this message littered throughout the logfile: ERROR: could not open relation pg_index_indexrelid_index: No such file or directory But, that doesn't seem to be effecting functionality or performance (especially considering the fact that the logfile that contains that message is part of the test that is performing better). We're using Postgres 7.4.8, building from the SLES9 Postgres 7.4.8 source rpm. Thanks for any help you can provide. I can provide more detail if needed. Thanks again, Bob ---(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 -- Jim Nasby[EMAIL PROTECTED] EnterpriseDB http://enterprisedb.com 512.569.9461 (cell) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[PERFORM] unsubscribe
unsubscribe Have you checked out the new-look www.indiatimes.com yet? ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [PERFORM] Unsubscribe
On Oct 4, 2006, at 10:54 AM, Joshua D. Drake wrote: [Joshua] It is ridiculous that this community expects people to read email headers to figure out how to unsubscribe from our lists. I always check the headers when I want to unsubscribe from any mailing list, and I think most people on this list have above average knowledge of such technical details. Of course, on a list with this many recepients there will always be some exceptions ... I would consider myself above average knowledge of such technical details and I didn't know the list information was in the headers until recently (the last time all of this came up). Now, I of course did know that there were headers, and I can use them to diagnose problems but I was unaware of an RFC that explicitly stated how the headers were supposed to be sent for mailing lists. However, that is besides the point. It is still ridiculous to expect anyone to read the headers just to unsubscribe from a list. If we didn't want to add it for each list we could just add a link here: http://www.postgresql.org/community/lists/subscribe An even better option would be to switch to a list manager that actively traps these emails, such as mailman. -- Jim Nasby[EMAIL PROTECTED] EnterpriseDB http://enterprisedb.com 512.569.9461 (cell) ---(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: [PERFORM] Unsubscribe
On Oct 4, 2006, at 11:35 AM, Csaba Nagy wrote: On Wed, 2006-10-04 at 18:02, Csaba Nagy wrote: If we didn't want to add it for each list we could just add a link here: http://www.postgresql.org/community/lists/subscribe OK, now that I had a second look on that page, it does contain unsubscription info... but it's well hidden for the fugitive look... the caption is a big Subscribe to Lists, you wouldn't think at a first glance think that the form is actually used to unsubscribe too, would you ? So maybe it's just that the text should be more explicit about what it actually does... Better yet, have an unsubscribe page... Personally, I'm tempted to get creative with procmail, and post a recipe that others can use to help enlighten those that post unsubscribe messages to the list... : -- Jim C. Nasby, Database Architect [EMAIL PROTECTED] 512.569.9461 (cell) http://jim.nasby.net ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[PERFORM] Unsubscribe
Please unsubscribe me! Thank you! Also, it would be better to have a message foot saying how to unsubscribe. ---(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: [PERFORM] Unsubscribe
On Wed, Oct 04, 2006 at 10:03:00 +0200, Luc Delgado [EMAIL PROTECTED] wrote: Please unsubscribe me! Thank you! If you really can't figure out how to unsubscribe from a list, you should contact the list owner, not the list. The list members can't unsubscribe you (and it isn't their job to) and the owner may not be subscribed to the list. The convention for lists is that adding '-owner' to the local part of the list email address will be an address for the owner. A good place to search to find out how to unsubscribe to a list is to search for the mailing lists using google. Usually the information on how to subscribe and unsubscribe are in the same place and you were able to find out how to subscribe in the first place, so you should be able to figure out how to unsubscribe by yourself as well. Also, it would be better to have a message foot saying how to unsubscribe. No, the standard is that the list information is kept in the headers so that it can be extracted by mail clients that care to. There is an RFC describing these headers. They are supplied by the mailing list software used for the Postgres mailing lists. Have your mail client display full headers for one of the list messages to get the instructions from there. ---(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: [PERFORM] Unsubscribe
Bruno Wolff III wrote: On Wed, Oct 04, 2006 at 10:03:00 +0200, Luc Delgado [EMAIL PROTECTED] wrote: Please unsubscribe me! Thank you! If you really can't figure out how to unsubscribe from a list, you should contact the list owner, not the list. The list members can't unsubscribe you (and it isn't their job to) and the owner may not be subscribed to the list. Although I 100% agree with you Bruno, it should be noted that our lists are a closed box for most people. They don't follow what is largely considered standard amongst lists which is to have list information at the bottom of each e-mail. It is ridiculous that this community expects people to read email headers to figure out how to unsubscribe from our lists. The convention for lists is that adding '-owner' to the local part of the list email address will be an address for the owner. A good place to search to find out how to unsubscribe to a list is to search for the mailing lists using google. Usually the information on how to subscribe and unsubscribe are in the same place and you were able to find out how to subscribe in the first place, so you should be able to figure out how to unsubscribe by yourself as well. Nobody should have to work that hard to unsubscribe. Also, it would be better to have a message foot saying how to unsubscribe. Yes, it definitely would. No, the standard is that the list information is kept in the headers so that it can be extracted by mail clients that care to. There is an RFC describing these headers. They are supplied by the mailing list software used for the Postgres mailing lists. Have your mail client display full headers for one of the list messages to get the instructions from there. Who the heck cares what the RFC says. The RFC is irrelevant if the mail clients don't support it. The clients that are most widely in use, do not support unsubscribing from lists via the email headers. Joshua D. Drake ---(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 -- === 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 5: don't forget to increase your free space map settings
Re: [PERFORM] Unsubscribe
To be a bit constructive, could it be an idea to add unsubscribe information as one of the standard tailer tips? Then unsubscribe info wouldn't appear in every mail, but often enough for people considering to unsubscribe. To be totally non-constructive, let me add a bit to the noise below: [Bruno] If you really can't figure out how to unsubscribe from a list, you should contact the list owner, not the list. The list members can't unsubscribe you (and it isn't their job to) and the owner may not be subscribed to the list. If he can't find out how to unsubscribe from the list, how can he be expected to figure out the owner address? [Joshua] It is ridiculous that this community expects people to read email headers to figure out how to unsubscribe from our lists. I always check the headers when I want to unsubscribe from any mailing list, and I think most people on this list have above average knowledge of such technical details. Of course, on a list with this many recepients there will always be some exceptions ... ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [PERFORM] Unsubscribe
This seems to be the nearly unanimous response to people posting an unsubscribe request to the postgres mailing lists. I emphatically agree with the argument - people should know better than that, and the information included in the e-mail headers should be more than sufficient. Every conceivable avenue of discovering how to unsubscribe, other than the list software attaching a footer on each e-mail, is available to pursue. I also don't care about that argument in this situation. People ignorantly posting an unsubscribe to the list get this kind of response because it's an annoyance to the list users, not necessarily because we care about educating that particular person. The posts obviously don't help future unsubscribers who aren't willing to track the information down anyway. We should be addressing this from the standpoint of what benefits long-term list users the most. The real question is: which is more annoying to list users, the occasional unsubscribe posted to the list (with accompanying responses), or a one-line footer on each post providing a link to unsubscribe instructions? Bruno Wolff III wrote: On Wed, Oct 04, 2006 at 10:03:00 +0200, Luc Delgado [EMAIL PROTECTED] wrote: Please unsubscribe me! Thank you! If you really can't figure out how to unsubscribe from a list, you should contact the list owner, not the list. The list members can't unsubscribe you (and it isn't their job to) and the owner may not be subscribed to the list. The convention for lists is that adding '-owner' to the local part of the list email address will be an address for the owner. A good place to search to find out how to unsubscribe to a list is to search for the mailing lists using google. Usually the information on how to subscribe and unsubscribe are in the same place and you were able to find out how to subscribe in the first place, so you should be able to figure out how to unsubscribe by yourself as well. Also, it would be better to have a message foot saying how to unsubscribe. No, the standard is that the list information is kept in the headers so that it can be extracted by mail clients that care to. There is an RFC describing these headers. They are supplied by the mailing list software used for the Postgres mailing lists. Have your mail client display full headers for one of the list messages to get the instructions from there. -- Nolan Cafferky Software Developer IT Department RBS Interactive [EMAIL PROTECTED]
Re: [PERFORM] Unsubscribe
[Joshua] It is ridiculous that this community expects people to read email headers to figure out how to unsubscribe from our lists. I always check the headers when I want to unsubscribe from any mailing list, and I think most people on this list have above average knowledge of such technical details. Of course, on a list with this many recepients there will always be some exceptions ... I would consider myself above average knowledge of such technical details and I didn't know the list information was in the headers until recently (the last time all of this came up). Now, I of course did know that there were headers, and I can use them to diagnose problems but I was unaware of an RFC that explicitly stated how the headers were supposed to be sent for mailing lists. However, that is besides the point. It is still ridiculous to expect anyone to read the headers just to unsubscribe from a list. If we didn't want to add it for each list we could just add a link here: http://www.postgresql.org/community/lists/subscribe Sincerely, Joshua D. Drake -- === 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 6: explain analyze is your friend
Re: [PERFORM] Unsubscribe
I also don't care about that argument in this situation. People ignorantly posting an unsubscribe to the list get this kind of response because it's an annoyance to the list users, Over time especially now, we will see many more users versus developers. Most users will never know how (nor should they have to) read email headers. benefits long-term list users the most. The real question is: which is more annoying to list users, the occasional unsubscribe posted to the list (with accompanying responses), or a one-line footer on each post providing a link to unsubscribe instructions? Good point, because I guarantee you every time someone pulls this elitist dung about email headers, I am going to step in and say something. So if you want to shut me up, lets get the footer added. Joshua D. Drake -- === 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 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [PERFORM] Unsubscribe
On Wed, Oct 04, 2006 at 08:30:03 -0700, Joshua D. Drake [EMAIL PROTECTED] wrote: Although I 100% agree with you Bruno, it should be noted that our lists are a closed box for most people. They don't follow what is largely considered standard amongst lists which is to have list information at the bottom of each e-mail. There are reasons you don't want to do that. Footers work OK for single part email messages. They don't make so much sense in multipart messages. You can probably take a crap shoot and add the footer to the first text/plain part and not break things. This won't work so well for multipart alternative messages that have text/plain and text/html parts. You could also try to insert a footer in to the html part, but thats a bit trickier since you can't just put it at the end. However, since the postgres lists are mostly just using text/plain parts for message bodies and there are already footers being used to distribute tips, it wouldn't make things significantly worse to add unsubscribe information as well. I would prefer just making the unsubscribe instructions easy to find on the web. ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [PERFORM] Unsubscribe
On Wed, 04 Oct 2006 09:00:45 -0700 Joshua D. Drake [EMAIL PROTECTED] wrote: So if you want to shut me up, lets get the footer added. Of course, that doesn't fix the problem 100%. I am on lists that do show that info in the footer and people still send unsubscribe messages to the list. By the way, mailman has a nice feature that sends messages that look like admin requests (such as unsubscribe) to the admin. That cuts down on the noise quite a bit. -- D'Arcy J.M. Cain darcy@druid.net | Democracy is three wolves http://www.druid.net/darcy/| and a sheep voting on +1 416 425 1212 (DoD#0082)(eNTP) | what's for dinner. ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [PERFORM] Unsubscribe
D'Arcy J.M. Cain wrote: On Wed, 04 Oct 2006 09:00:45 -0700 Joshua D. Drake [EMAIL PROTECTED] wrote: So if you want to shut me up, lets get the footer added. Of course, that doesn't fix the problem 100%. I am on lists that do show that info in the footer and people still send unsubscribe messages to the list. Sure, but what is more helpful? A reply that snips everything but the footer that has those instructions or a replay that shows email headers that look basically like some weird code to users? By the way, mailman has a nice feature that sends messages that look like admin requests (such as unsubscribe) to the admin. That cuts down on the noise quite a bit. Well you don't have to convince me to use mailman ;)... but the *ahem* list administrators of this project would rather have their toenails removed with a dull spoon. Sincerely, Joshua D. Drake -- === 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 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [PERFORM] Unsubscribe
I would prefer just making the unsubscribe instructions easy to find on the web. They actually reasonably are. If you go to www-community/support-lists Sincerely, 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: [PERFORM] Unsubscribe
I'd prefer to have a short footer link called something like Mailing List Page which would take you to a page where you could subscribe, unsubscribe, or view the archives. I think that making the link short and also making it a quick shortcut away from the archives tips the scales in terms of utility vs. annoyance. One of the tips that shows up in the footers today is just a link to the archives anyway. -- Mark Lewis On Wed, 2006-10-04 at 11:28 -0500, Bruno Wolff III wrote: On Wed, Oct 04, 2006 at 08:30:03 -0700, Joshua D. Drake [EMAIL PROTECTED] wrote: Although I 100% agree with you Bruno, it should be noted that our lists are a closed box for most people. They don't follow what is largely considered standard amongst lists which is to have list information at the bottom of each e-mail. There are reasons you don't want to do that. Footers work OK for single part email messages. They don't make so much sense in multipart messages. You can probably take a crap shoot and add the footer to the first text/plain part and not break things. This won't work so well for multipart alternative messages that have text/plain and text/html parts. You could also try to insert a footer in to the html part, but thats a bit trickier since you can't just put it at the end. However, since the postgres lists are mostly just using text/plain parts for message bodies and there are already footers being used to distribute tips, it wouldn't make things significantly worse to add unsubscribe information as well. I would prefer just making the unsubscribe instructions easy to find on the web. ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [PERFORM] Unsubscribe
On Wed, 2006-10-04 at 18:02, Csaba Nagy wrote: If we didn't want to add it for each list we could just add a link here: http://www.postgresql.org/community/lists/subscribe OK, now that I had a second look on that page, it does contain unsubscription info... but it's well hidden for the fugitive look... the caption is a big Subscribe to Lists, you wouldn't think at a first glance think that the form is actually used to unsubscribe too, would you ? So maybe it's just that the text should be more explicit about what it actually does... Cheers, Csaba. ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [PERFORM] Unsubscribe
On Oct 4, 2006, at 9:00 AM, Joshua D. Drake wrote: I also don't care about that argument in this situation. People ignorantly posting an unsubscribe to the list get this kind of response because it's an annoyance to the list users, Over time especially now, we will see many more users versus developers. Most users will never know how (nor should they have to) read email headers. They should know how to participate in mailing lists. That's unrelated to whether you're a developer or a user. The same webpage where you subscribe to a mailing list, you can also unsubscribe. This is not some weird technical voodoo, just that some people prefer to waste a thousand other peoples time than spend a minute or two of their own. Fortunately, they're a tiny minority. benefits long-term list users the most. The real question is: which is more annoying to list users, the occasional unsubscribe posted to the list (with accompanying responses), or a one-line footer on each post providing a link to unsubscribe instructions? Good point, because I guarantee you every time someone pulls this elitist dung about email headers, I am going to step in and say something. So if you want to shut me up, lets get the footer added. Judging from experience on other lists, it won't help. The tiny minority of people who are unable to unsubscribe will continue to be unable to unsubscribe. It won't hurt, though. Cheers, Steve ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [PERFORM] Unsubscribe
Steve Atkins wrote: On Oct 4, 2006, at 9:00 AM, Joshua D. Drake wrote: I also don't care about that argument in this situation. People ignorantly posting an unsubscribe to the list get this kind of response because it's an annoyance to the list users, Over time especially now, we will see many more users versus developers. Most users will never know how (nor should they have to) read email headers. They should know how to participate in mailing lists. That's unrelated to whether you're a developer or a user. The same webpage where you subscribe to a mailing list, you can also unsubscribe. This is not some weird technical voodoo, just that some people prefer to waste a thousand other peoples time than spend a minute or two of their own. Fortunately, they're a tiny minority. I believe that if you could get an honest response, you'd find a lot of these folks are just plain lazy. They don't want to recall how to unsubscribe and figure sending mail to the list will get the required result. -- Until later, Geoffrey Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. - Benjamin Franklin ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [PERFORM] Unsubscribe
On Wed, Oct 04, 2006 at 08:30:03AM -0700, Joshua D. Drake wrote: They don't follow what is largely considered standard amongst lists which is to have list information at the bottom of each e-mail. In my experience such a footer doesn't do much to prevent people sending unsubscribe messages to the list. Mike Stone ---(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: [PERFORM] Unsubscribe
uwcssa wrote: Please unsubscribe me! Thank you! Also, it would be better to have a message foot saying how to unsubscribe. It would be better if you would have paid attention when you subscribed as to how to unsubscribe. -- Until later, Geoffrey Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. - Benjamin Franklin ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [PERFORM] Unsubscribe
On Mon, Oct 02, 2006 at 01:36:17PM -0400, uwcssa wrote: Please unsubscribe me! Thank you! Also, it would be better to have a message foot saying how to unsubscribe. Will this do? It's too big for a footer. Here's how to unsubscribe: First, ask your Internet Provider to mail you an Unsubscribing Kit. Then follow these directions. The kit will most likely be the standard no-fault type. Depending on requirements, System A and/or System B can be used. When operating System A, depress lever and a plastic dalkron unsubscriber will be dispensed through the slot immediately underneath. When you have fastened the adhesive lip, attach connection marked by the large X outlet hose. Twist the silver-coloured ring one inch below the connection point until you feel it lock. The kit is now ready for use. The Cin-Eliminator is activated by the small switch on the lip. When securing, twist the ring back to its initial condition, so that the two orange lines meet. Disconnect. Place the dalkron unsubscriber in the vacuum receptacle to the rear. Activate by pressing the blue button. The controls for System B are located on the opposite side. The red release switch places the Cin-Eliminator into position; it can be adjusted manually up or down by pressing the blue manual release button. The opening is self-adjusting. To secure after use, press the green button, which simultaneously activates the evaporator and returns the Cin-Eliminator to its storage position. You may log off if the green exit light is on over the evaporator. If the red light is illuminated, one of the Cin-Eliminator requirements has not been properly implemented. Press the List Guy call button on the right of the evaporator. He will secure all facilities from his control panel. To use the Auto-Unsub, first undress and place all your clothes in the clothes rack. Put on the velcro slippers located in the cabinet immediately below. Enter the shower, taking the entire kit with you. On the control panel to your upper right upon entering you will see a Shower seal button. Press to activate. A green light will then be illuminated immediately below. On the intensity knob, select the desired setting. Now depress the Auto-Unsub activation lever. Bathe normally. The Auto-Unsub will automatically go off after three minutes unless you activate the Manual off override switch by flipping it up. When you are ready to leave, press the blue Shower seal release button. The door will open and you may leave. Please remove the velcro slippers and place them in their container. If you prefer the ultrasonic log-off mode, press the indicated blue button. When the twin panels open, pull forward by rings A B. The knob to the left, just below the blue light, has three settings, low, medium or high. For normal use, the medium setting is suggested. After these settings have been made, you can activate the device by switching to the ON position the clearly marked red switch. If during the unsubscribing operation you wish to change the settings, place the manual off override switch in the OFF position. You may now make the change and repeat the cycle. When the green exit light goes on, you may log off and have lunch. Please close the door behind you. -- ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._. Felix Finch: scarecrow repairman rocket surgeon / [EMAIL PROTECTED] GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933 I've found a solution to Fermat's Last Theorem but I see I've run out of room o ---(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: [PERFORM] Unsubscribe
I got one of these last Christmas. It works great, but the device has no obvious power source and now I can't find my cat. God help me when I accidently try to unsubscribe like that .. Carlo [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] On Mon, Oct 02, 2006 at 01:36:17PM -0400, uwcssa wrote: Please unsubscribe me! Thank you! Also, it would be better to have a message foot saying how to unsubscribe. Will this do? It's too big for a footer. Here's how to unsubscribe: First, ask your Internet Provider to mail you an Unsubscribing Kit. Then follow these directions. The kit will most likely be the standard no-fault type. Depending on requirements, System A and/or System B can be used. When operating System A, depress lever and a plastic dalkron unsubscriber will be dispensed through the slot immediately underneath. When you have fastened the adhesive lip, attach connection marked by the large X outlet hose. Twist the silver-coloured ring one inch below the connection point until you feel it lock. The kit is now ready for use. The Cin-Eliminator is activated by the small switch on the lip. When securing, twist the ring back to its initial condition, so that the two orange lines meet. Disconnect. Place the dalkron unsubscriber in the vacuum receptacle to the rear. Activate by pressing the blue button. The controls for System B are located on the opposite side. The red release switch places the Cin-Eliminator into position; it can be adjusted manually up or down by pressing the blue manual release button. The opening is self-adjusting. To secure after use, press the green button, which simultaneously activates the evaporator and returns the Cin-Eliminator to its storage position. You may log off if the green exit light is on over the evaporator. If the red light is illuminated, one of the Cin-Eliminator requirements has not been properly implemented. Press the List Guy call button on the right of the evaporator. He will secure all facilities from his control panel. To use the Auto-Unsub, first undress and place all your clothes in the clothes rack. Put on the velcro slippers located in the cabinet immediately below. Enter the shower, taking the entire kit with you. On the control panel to your upper right upon entering you will see a Shower seal button. Press to activate. A green light will then be illuminated immediately below. On the intensity knob, select the desired setting. Now depress the Auto-Unsub activation lever. Bathe normally. The Auto-Unsub will automatically go off after three minutes unless you activate the Manual off override switch by flipping it up. When you are ready to leave, press the blue Shower seal release button. The door will open and you may leave. Please remove the velcro slippers and place them in their container. If you prefer the ultrasonic log-off mode, press the indicated blue button. When the twin panels open, pull forward by rings A B. The knob to the left, just below the blue light, has three settings, low, medium or high. For normal use, the medium setting is suggested. After these settings have been made, you can activate the device by switching to the ON position the clearly marked red switch. If during the unsubscribing operation you wish to change the settings, place the manual off override switch in the OFF position. You may now make the change and repeat the cycle. When the green exit light goes on, you may log off and have lunch. Please close the door behind you. -- ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._. Felix Finch: scarecrow repairman rocket surgeon / [EMAIL PROTECTED] GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933 I've found a solution to Fermat's Last Theorem but I see I've run out of room o ---(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 ---(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
[PERFORM] Unsubscribe
Please unsubscribe me! Thank you! Also, it would be better to have a message foot saying how to unsubscribe.
Re: [PERFORM] Unsubscribe
Hi, Uwcssa, uwcssa wrote: Please unsubscribe me! Thank you! Sorry, but we (the list members) are unable do that, we have no adminstrative power on the list. :-( Also, it would be better to have a message foot saying how to unsubscribe. List unsubscribe information is contained in the Headers of every mail that's sent over the list: List-Archive: http://archives.postgresql.org/pgsql-performance List-Help: mailto:[EMAIL PROTECTED] List-ID: pgsql-performance.postgresql.org List-Owner: mailto:[EMAIL PROTECTED] List-Post: mailto:pgsql-performance@postgresql.org List-Subscribe: mailto:[EMAIL PROTECTED] List-Unsubscribe: mailto:[EMAIL PROTECTED] Additionally, there is a link to the unsubscribe web form at the list archive page: http://archives.postgresql.org/pgsql-performance/ HTH, Markus ---(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
[PERFORM] Unsubscribe
---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [PERFORM] Unsubscribe
http://www.postgresql.org/community/lists/ http://www.postgresql.org/community/lists/subscribe -- Until later, Geoffrey Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. - Benjamin Franklin ---(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
[PERFORM] unsubscribe me
hi plz unsubscribe me.. i am sending mail to this id.. for unsubscribing.. is it correct.. my mail box is gettin flooded..
Re: [PERFORM] unsubscribe me
Phadnis shphadnis 'at' rediffmail.com writes: plz unsubscribe me.. i am sending mail to this id.. for unsubscribing.. is it correct.. my mail box is gettin flooded.. you managed to subscribe, you'll probably manage to unsubcribe. hint: the email headers contain the information for unsubscribing. -- Guillaume Cottenceau Create your personal SMS or WAP Service - visit http://mobilefriends.ch/ ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[PERFORM] unsubscribe
-- Forwarded message --From: Gourish Singbal [EMAIL PROTECTED]Date: Aug 9, 2006 12:24 PM Subject: unsubscribeTo: pgsql-admin@postgresql.org pgsql-admin@postgresql.org -- Best, Gourish Singbal -- Best,Gourish Singbal
[PERFORM] Unsubscribe
Unsubscribe -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.10.8/413 - Release Date: 2006/08/08 ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[PERFORM] unsubscribe
unsubscribe -- Wade Klaver Wavefire Technologies Corporation GPG Public Key at http://archeron.wavefire.com /\ ASCII Ribbon Campaign . \ / - NO HTML/RTF in e-mail . X - NO Word docs in e-mail . / \ - ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[PERFORM] Unsubscribe
Best regards, Jamal ---(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: [PERFORM] unsubscribe
Unsubscribe From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Diego Gaviola Sent: Tuesday, June 27, 2006 4:15 AM To: pgsql-performance@postgresql.org Subject: [PERFORM] unsubscribe unsubscribe
[PERFORM] unsubscribe
---(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
[PERFORM] unsubscribe
[PERFORM] unsubscribe
-- Lorenzo PasquinelliSoftware Developer My grandfather once told me that there are two kinds of people: thosewho work and those who take the credit. He told me to try to be in thefirst group; there was less competition there.- Indira Gandhi
[PERFORM] unsubscribe
unsubscribe
Re: [PERFORM] UNSUBSCRIBE
On May 10, 2006, at 14:42 , Tom Lane wrote: Chris [EMAIL PROTECTED] writes: Maybe :) The php-general list has To unsubscribe, visit: http://www.php.net/unsub.php at the bottom of every email, and there are still random unsubscribe requests.. That will *always* happen. Just human nature and the numbers of subscribers. However, a one-liner that either points to the webpage for unsubscribing (probably easiest) or a brief description on how to unsubscribe (To unsubscribe, send an email to [EMAIL PROTECTED] with body unsub pgsql-performance (without quotes)) may intercept a few more. Is there a way to configure Majordomo to make even easier to unsubscribe? Just sending to pgsql- [EMAIL PROTECTED] or some such? I've seen other mailing lists that do this. Requiring a specific command (what's the command? in the subject or the body?) is one more place a person can make a mistake. (I've recently switched mail accounts and unsubbed/ subbed from the lists I'm on. This latter style does make it a lot easier.) (And are there mail readers out there that can pick those subscribe/ unsubscribe headers from the list emails? Now *that'd* be sweet.) Michael Glaesemann grzm seespotcode net ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [PERFORM] UNSUBSCRIBE
On Wed, May 10, 2006 at 01:15:11 -0400, Tom Lane [EMAIL PROTECTED] wrote: Maybe the real problem is at the other end of the process, ie we should require some evidence of a greater-than-room-temp IQ to subscribe in the first place? I suspect it is more lazyiness that smarts. That had to at least figure out how to respond to the confirm message in the first place in order to get subscribed. My theory is that they don't want to take the trouble to figure out how to unsubscribe when they (think that they) can just send a message to the list (not even the admin) asking to be unsubscribed and it will (well actually won't on these lists) happen. Maybe posts with unsubscribe in the subject could be held for moderation and/or get an automated reply with instructions for unsubscribing. ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [PERFORM] UNSUBSCRIBE
On Wed, May 10, 2006 at 11:10:37AM -0400, Tom Lane wrote: Michael Glaesemann [EMAIL PROTECTED] writes: (And are there mail readers out there that can pick those subscribe/ unsubscribe headers from the list emails? Now *that'd* be sweet.) Well, in my fairly ancient copy of exmh, any message with such headers causes an additional menu to appear: Based on the constantly broken threading in the lists, I'd bet that less than 20% of posters use something more sophisticated than MS LookOut!, and I'm sure that the stats for subscribers are far worse. Does majordomo have an option to automagically handle such posts that are sent to the post address instead of the admin address? I know mailman can do that... -- 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 4: Have you searched our list archives? http://archives.postgresql.org
[PERFORM] UNSUBSCRIBE
UNSUBSCRIBE ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [PERFORM] UNSUBSCRIBE
Shoaib Burq wrote: UNSUBSCRIBE To unsubscribe: List-Unsubscribe: mailto:[EMAIL PROTECTED] Email admins - Could we add this above or below the random tips that get appended to every email ? -- Postgresql php tutorials http://www.designmagick.com/ ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [PERFORM] UNSUBSCRIBE
Chris [EMAIL PROTECTED] writes: Email admins - Could we add this above or below the random tips that get appended to every email ? You mean like these headers that already get added to every list message (these copied-and-pasted from your own message): List-help: mailto:[EMAIL PROTECTED] List-owner: mailto:[EMAIL PROTECTED] List-subscribe: mailto:[EMAIL PROTECTED] List-unsubscribe: mailto:[EMAIL PROTECTED] Plus there are at least two of the random tips that deal with how to unsubscribe. My feeling is that the people who can't figure this out still won't figure it out, no matter how thick the cluebat we swing at them :-( Maybe the real problem is at the other end of the process, ie we should require some evidence of a greater-than-room-temp IQ to subscribe in the first place? regards, tom lane ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [PERFORM] UNSUBSCRIBE
Tom Lane wrote: Chris [EMAIL PROTECTED] writes: Email admins - Could we add this above or below the random tips that get appended to every email ? You mean like these headers that already get added to every list message (these copied-and-pasted from your own message): The headers aren't the first place you'd go looking for such info.. once you know they are there it's ok. Maybe the real problem is at the other end of the process, ie we should require some evidence of a greater-than-room-temp IQ to subscribe in the first place? Maybe :) The php-general list has To unsubscribe, visit: http://www.php.net/unsub.php at the bottom of every email, and there are still random unsubscribe requests.. Ah well :) -- Postgresql php tutorials http://www.designmagick.com/ ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [PERFORM] UNSUBSCRIBE
Chris [EMAIL PROTECTED] writes: Tom Lane wrote: Maybe the real problem is at the other end of the process, ie we should require some evidence of a greater-than-room-temp IQ to subscribe in the first place? Maybe :) The php-general list has To unsubscribe, visit: http://www.php.net/unsub.php at the bottom of every email, and there are still random unsubscribe requests.. That's depressing, indeed :-( I'm not against spending a little bandwidth to provide unsub instructions, but somehow I can't see putting an 8x10 color glossy photograph with circles and arrows and a paragraph on the back [1] of every list message to do it. regards, tom lane [1] http://www.guntheranderson.com/v/data/alicesre.htm ---(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
[PERFORM] unsubscribe
unsubscribe ---(end of broadcast)--- TIP 6: explain analyze is your friend
[PERFORM] unsubscribe
unsubscribe
[PERFORM] unsubscribe
unsubscribe
[PERFORM] unsubscribe
unsubscribe ---(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
[PERFORM] UNSUBSCRIBE
UNSUBSCRIBE ---(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
[PERFORM] unsubscribe
unsubscribe ---(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
[PERFORM] unsubscribe
unsubscribe ---(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 Nelba Sánchez R. Servicios Tecnológicos de Gestión (STG) Pontificia Universidad Católica de Chile fono : (56-2) 686 2316 fax : (56-2) 222 9487 mailto:[EMAIL PROTECTED] ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[PERFORM] unsubscribe
unsubscribe-digest
[PERFORM] unsubscribe
unsubscribe-digest ---(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
[PERFORM] unsubscribe
-- Don Vaillancourt Director of Software Development WEB IMPACT INC. phone: 416-815-2000 ext. 245 fax: 416-815-2001 email: [EMAIL PROTECTED] web: http://www.web-impact.com address: http://www.mapquest.ca This email message is intended only for the addressee(s) and contains information that may be confidential and/or copyright. If you are not the intended recipient please notify the sender by reply email and immediately delete this email. Use, disclosure or reproduction of this email by anyone other than the intended recipient(s) is strictly prohibited. No representation is made that this email or any attachments are free of viruses. Virus scanning is recommended and is the responsibility of the recipient.
[PERFORM] UNSUBSCRIBE
---(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
[PERFORM] Unsubscribe
Unsubscribe ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
