Re: [HACKERS] psql possible TODO
Bruce Momjian wrote: Added to TODO: o Add \# to list command history like \s, but with line numbers http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php Humm, this is not what we agreed. --- Joshua D. Drake wrote: Hello, O.k. this is my currently thinking: \# will list just like \s except it will include line numbers: 1 SELECT * FROM FOO; (not a tab of course) 2 UPDATE bar SET foo = 6; \# 2will execute query number 2 \#e 2 will open the numbered query in $EDITOR I would love to figure out a way to auto explain these queries without obnoxious syntax. Any ideas? -- Alvaro Herrerahttp://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [HACKERS] psql possible TODO
Alvaro Herrera wrote: Bruce Momjian wrote: Added to TODO: o Add \# to list command history like \s, but with line numbers http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php Humm, this is not what we agreed. Actually to be fair, there was no agreement. However, I do think it is not worthwhile to be a TODO (thank you anyway Bruce). I am not going to be spending my time on it and I doubt anyone else will. Joshua D. Drake --- Joshua D. Drake wrote: Hello, O.k. this is my currently thinking: \# will list just like \s except it will include line numbers: 1 SELECT * FROM FOO; (not a tab of course) 2 UPDATE bar SET foo = 6; \# 2will execute query number 2 \#e 2 will open the numbered query in $EDITOR I would love to figure out a way to auto explain these queries without obnoxious syntax. Any ideas? -- === 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/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/ ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] psql possible TODO
Alvaro Herrera wrote: Bruce Momjian wrote: Added to TODO: o Add \# to list command history like \s, but with line numbers http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php Humm, this is not what we agreed. Are you saying the URL is wrong or the description? I have updated the item description to: o Add \# to list and execute command history -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
Re: [HACKERS] psql possible TODO
Joshua D. Drake wrote: Alvaro Herrera wrote: Bruce Momjian wrote: Added to TODO: o Add \# to list command history like \s, but with line numbers http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php Humm, this is not what we agreed. Actually to be fair, there was no agreement. However, I do think it is not worthwhile to be a TODO (thank you anyway Bruce). I am not going to be spending my time on it and I doubt anyone else will. Really, I thought there were a number of people who liked it. New text is: o Add \# to list and execute command history Are you sure you want it removed? --- Joshua D. Drake --- Joshua D. Drake wrote: Hello, O.k. this is my currently thinking: \#will list just like \s except it will include line numbers: 1 SELECT * FROM FOO; (not a tab of course) 2 UPDATE bar SET foo = 6; \# 2 will execute query number 2 \#e 2 will open the numbered query in $EDITOR I would love to figure out a way to auto explain these queries without obnoxious syntax. Any ideas? -- === 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/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/ -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] psql possible TODO
Bruce Momjian wrote: Alvaro Herrera wrote: Bruce Momjian wrote: Added to TODO: o Add \# to list command history like \s, but with line numbers http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php Humm, this is not what we agreed. Are you saying the URL is wrong or the description? I have updated the item description to: o Add \# to list and execute command history I guess what I am saying is that I asked you two times to add the TODO entry that was agreed and you ignored me. -- Alvaro Herrerahttp://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] psql possible TODO
Alvaro Herrera wrote: Bruce Momjian wrote: Alvaro Herrera wrote: Bruce Momjian wrote: Added to TODO: o Add \# to list command history like \s, but with line numbers http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php Humm, this is not what we agreed. Are you saying the URL is wrong or the description? I have updated the item description to: o Add \# to list and execute command history I guess what I am saying is that I asked you two times to add the TODO entry that was agreed and you ignored me. I did not ignore you --- I replied I was getting to it, and now you are not telling me what the TODO wording should be, and now Joshua Drake doesn't want it. I see this email you sent me: - Allow psql to display item numbers along each history item, depending on a \set variable So that is what we agreed to? OK, old item removed, and this added: o Add a \set variable to control whether \s displays line numbers Also, Alvaro, feel free to add TODO items yourself. There is nothing special about me adding a TODO item except that I update the HTML, but if I see a commit to TODO, I update TODO.html. -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
Re: [HACKERS] psql possible TODO
I am not going to be spending my time on it and I doubt anyone else will. Really, I thought there were a number of people who liked it. New text is: o Add \# to list and execute command history Are you sure you want it removed? Well let me put it this way. I think my idea was good, I came up with it ;). There are others that felt it was good to. On reviewing the thread, you are correct and it should probably remain a TODO. I just won't get to it before feature freeze. 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/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/ ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] psql possible TODO
Joshua D. Drake wrote: I am not going to be spending my time on it and I doubt anyone else will. Really, I thought there were a number of people who liked it. New text is: o Add \# to list and execute command history Are you sure you want it removed? Well let me put it this way. I think my idea was good, I came up with it ;). There are others that felt it was good to. On reviewing the thread, you are correct and it should probably remain a TODO. I just won't get to it before feature freeze. OK, merged TODO: o Add a \set variable to control whether \s displays line numbers Another option is to add \# which lists line numbers, and allows command execution. http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php -- 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] psql possible TODO
Added to TODO: o Add \# to list command history like \s, but with line numbers http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php --- Joshua D. Drake wrote: Hello, O.k. this is my currently thinking: \#will list just like \s except it will include line numbers: 1 SELECT * FROM FOO; (not a tab of course) 2 UPDATE bar SET foo = 6; \# 2 will execute query number 2 \#e 2 will open the numbered query in $EDITOR I would love to figure out a way to auto explain these queries without obnoxious syntax. Any ideas? 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/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate ---(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 -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] psql possible TODO
Joshua D. Drake wrote: On Fri, 2006-12-29 at 20:59 -0500, Bruce Momjian wrote: Alvaro Herrera wrote: Tom Lane wrote: Richard Troy [EMAIL PROTECTED] writes: ... it occurs to me that perhaps Josh can implement a command line switch to turn on command line numbering. That would solve the problem I have with changing \s. I think a psql \set variable (comparable to ON_ERROR_STOP and friends) might be the way to go instead of inventing another \-command, but it's not real important. So, is anybody working on this? I think it should be put in the TODO list: - Allow psql to display item numbers along each history item, depending on a \set variable I thought Joshua Drake was going to submit a patch, but if doesn't appear shortly, I will add it to the TODO list with the agreed API. I will claim this for now. I will let it go if I can't get at least something productive done on it by end of January. Now that the embargo period seems to be over, I think it would be a good time to add it to the TODO list. Also, I'd modify the idea slightly to allow a more general facility, using %-escapes (or similar) for line numbers, dates and so on. Bash allows something like this (albeit limited to only times) using the HISTTIMEFORMAT environment variable. This is the first case I know of of an embargo to an agreed TODO item. Why was it put in place? I find it distracting, because the item has to be put on someone else's TODO list and then that person has to pinch others to get it added to the central TODO list. Not sure I see the point. (I understand about bashing Joshua ---a sport I also practice in Command Prompt's internal lists ;-) --- but in this case it seems to be counterproductive). -- Alvaro Herrerahttp://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. ---(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] psql possible TODO
It is actually still in my mailbox to be added to TODO when I get up to it. --- Alvaro Herrera wrote: Joshua D. Drake wrote: On Fri, 2006-12-29 at 20:59 -0500, Bruce Momjian wrote: Alvaro Herrera wrote: Tom Lane wrote: Richard Troy [EMAIL PROTECTED] writes: ... it occurs to me that perhaps Josh can implement a command line switch to turn on command line numbering. That would solve the problem I have with changing \s. I think a psql \set variable (comparable to ON_ERROR_STOP and friends) might be the way to go instead of inventing another \-command, but it's not real important. So, is anybody working on this? I think it should be put in the TODO list: - Allow psql to display item numbers along each history item, depending on a \set variable I thought Joshua Drake was going to submit a patch, but if doesn't appear shortly, I will add it to the TODO list with the agreed API. I will claim this for now. I will let it go if I can't get at least something productive done on it by end of January. Now that the embargo period seems to be over, I think it would be a good time to add it to the TODO list. Also, I'd modify the idea slightly to allow a more general facility, using %-escapes (or similar) for line numbers, dates and so on. Bash allows something like this (albeit limited to only times) using the HISTTIMEFORMAT environment variable. This is the first case I know of of an embargo to an agreed TODO item. Why was it put in place? I find it distracting, because the item has to be put on someone else's TODO list and then that person has to pinch others to get it added to the central TODO list. Not sure I see the point. (I understand about bashing Joshua ---a sport I also practice in Command Prompt's internal lists ;-) --- but in this case it seems to be counterproductive). -- Alvaro Herrerahttp://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. ---(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 -- 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] psql possible TODO
Alvaro Herrera wrote: I will claim this for now. I will let it go if I can't get at least something productive done on it by end of January. Now that the embargo period seems to be over, I think it would be a good time to add it to the TODO list. Also, I'd modify the idea slightly to allow a more general facility, using %-escapes (or similar) for line numbers, dates and so on. Bash allows something like this (albeit limited to only times) using the HISTTIMEFORMAT environment variable. This is the first case I know of of an embargo to an agreed TODO item. Why was it put in place? I find it distracting, because the item has to be put on someone else's TODO list and then that person has to pinch others to get it added to the central TODO list. Not sure I see the point. (I understand about bashing Joshua ---a sport I also practice in Command Prompt's internal lists ;-) --- but in this case it seems to be counterproductive). The only reason it isn't on the TODO is because I am still catching up for the 8.3 queue. I know of no embargo. -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [HACKERS] psql possible TODO
Tom Lane wrote: Richard Troy [EMAIL PROTECTED] writes: ... it occurs to me that perhaps Josh can implement a command line switch to turn on command line numbering. That would solve the problem I have with changing \s. I think a psql \set variable (comparable to ON_ERROR_STOP and friends) might be the way to go instead of inventing another \-command, but it's not real important. So, is anybody working on this? I think it should be put in the TODO list: - Allow psql to display item numbers along each history item, depending on a \set variable -- Alvaro Herrerahttp://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support ---(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] psql possible TODO
Alvaro Herrera wrote: Tom Lane wrote: Richard Troy [EMAIL PROTECTED] writes: ... it occurs to me that perhaps Josh can implement a command line switch to turn on command line numbering. That would solve the problem I have with changing \s. I think a psql \set variable (comparable to ON_ERROR_STOP and friends) might be the way to go instead of inventing another \-command, but it's not real important. So, is anybody working on this? I think it should be put in the TODO list: - Allow psql to display item numbers along each history item, depending on a \set variable I thought Joshua Drake was going to submit a patch, but if doesn't appear shortly, I will add it to the TODO list with the agreed API. -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [HACKERS] psql possible TODO
On Fri, 2006-12-29 at 20:59 -0500, Bruce Momjian wrote: Alvaro Herrera wrote: Tom Lane wrote: Richard Troy [EMAIL PROTECTED] writes: ... it occurs to me that perhaps Josh can implement a command line switch to turn on command line numbering. That would solve the problem I have with changing \s. I think a psql \set variable (comparable to ON_ERROR_STOP and friends) might be the way to go instead of inventing another \-command, but it's not real important. So, is anybody working on this? I think it should be put in the TODO list: - Allow psql to display item numbers along each history item, depending on a \set variable I thought Joshua Drake was going to submit a patch, but if doesn't appear shortly, I will add it to the TODO list with the agreed API. I will claim this for now. I will let it go if I can't get at least something productive done on it by end of January. 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/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
