Re: [HACKERS] Change Request: \pset pager off in pg_dumpall
Your pg_dump's actually invoke the pager? Are you manually starting psql, then doing \i dumpfile? Why would you do that rather than psql template1 dumpfile? Because I'm a dork :-). Seriously, sometimes it's useful. The most useful reason (and I wish you could turn it on with psql file) is the line number in the file where any errors occur. (TODO item?) Chris ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] Change Request: \pset pager off in pg_dumpall
Larry Rosenman [EMAIL PROTECTED] writes: On Mon, 11 Aug 2003, Bruce Momjian wrote: Larry Rosenman wrote: Can we modify pg_dumpall (or pg_dump?) to include a \pset pager off to prevent the setval() calls from halting an interactive \i of the dump file? Your pg_dump's actually invoke the pager? Seriously, sometimes it's useful. Are you using any nonstandard settings in ~/.psqlrc? I've never seen this happen myself. regards, tom lane ---(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] Change Request: \pset pager off in pg_dumpall
Christopher Kings-Lynne writes: The most useful reason (and I wish you could turn it on with psql file) is the line number in the file where any errors occur. psql -f file will do that. -- Peter Eisentraut [EMAIL PROTECTED] ---(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] Change Request: \pset pager off in pg_dumpall
--On Tuesday, August 12, 2003 09:30:39 -0400 Tom Lane [EMAIL PROTECTED] wrote: Larry Rosenman [EMAIL PROTECTED] writes: Nope. There is no .psqlrc. It seems to be new with 7.4cvs. (dunno about earlier 7.4), but it definitely did NOT happen with 7.3.x Hmph. There have been some changes in 7.4 psql's pager support, but I can't see anything there that looks like it would cause this. And it (still) doesn't happen on my machine. Would you trace through PageOutput and see why it's deciding to use the pager for short output? seems to do it for ANY SRF, if that helps any. I.E. \d, and show all;. LER regards, tom lane -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 ---(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] Change Request: \pset pager off in pg_dumpall
Larry Rosenman [EMAIL PROTECTED] writes: Nope. There is no .psqlrc. It seems to be new with 7.4cvs. (dunno about earlier 7.4), but it definitely did NOT happen with 7.3.x Hmph. There have been some changes in 7.4 psql's pager support, but I can't see anything there that looks like it would cause this. And it (still) doesn't happen on my machine. Would you trace through PageOutput and see why it's deciding to use the pager for short output? regards, tom lane ---(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] Change Request: \pset pager off in pg_dumpall
On Mon, 11 Aug 2003, Bruce Momjian wrote: Larry Rosenman wrote: Can we modify pg_dumpall (or pg_dump?) to include a \pset pager off to prevent the setval() calls from halting an interactive \i of the dump file? Your pg_dump's actually invoke the pager? Are you manually starting psql, then doing \i dumpfile? Why would you do that rather than psql template1 dumpfile? Because I'm a dork :-). Seriously, sometimes it's useful. LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[HACKERS] Change Request: \pset pager off in pg_dumpall
Can we modify pg_dumpall (or pg_dump?) to include a \pset pager off to prevent the setval() calls from halting an interactive \i of the dump file? Thanks, LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] Change Request: \pset pager off in pg_dumpall
Larry Rosenman wrote: Can we modify pg_dumpall (or pg_dump?) to include a \pset pager off to prevent the setval() calls from halting an interactive \i of the dump file? Your pg_dump's actually invoke the pager? Are you manually starting psql, then doing \i dumpfile? Why would you do that rather than psql template1 dumpfile? -- 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 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] Change Request: \pset pager off in pg_dumpall
--On Monday, August 11, 2003 20:36:11 -0400 Tom Lane [EMAIL PROTECTED] wrote: Larry Rosenman [EMAIL PROTECTED] writes: On Mon, 11 Aug 2003, Bruce Momjian wrote: Larry Rosenman wrote: Can we modify pg_dumpall (or pg_dump?) to include a \pset pager off to prevent the setval() calls from halting an interactive \i of the dump file? Your pg_dump's actually invoke the pager? Seriously, sometimes it's useful. Are you using any nonstandard settings in ~/.psqlrc? I've never seen this happen myself. Nope. There is no .psqlrc. It seems to be new with 7.4cvs. (dunno about earlier 7.4), but it definitely did NOT happen with 7.3.x LER regards, tom lane -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
