Re: [HACKERS] psql: recall previous command?

One interesting artifact of using \e to edit a multi-line command is that the same command is then treated as a single-line command in subsequent up-arrow or Ctrl-P attempts. I use this frequently to achieve a similar effect to what you're after. The one downside is that if you leave the psql

Re: [HACKERS] Where to see the patch queue (was Re: [PATCHES] Patch

I have a feeling Bruce was referring to item 1.4: http://developer.postgresql.org/readtext.php?src/FAQ/ FAQ_DEV.html+Developers-FAQ#1.4 -tfo -- Thomas F. O'Connell Co-Founder, Information Architect Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320

Novice Slony User (Was [HACKERS] hi all)

First things first: try posting to the Slony mailing list: [EMAIL PROTECTED] -tfo -- Thomas F. O'Connell Co-Founder, Information Architect Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-260-0005 On Mar 2, 2005, at 7:23 PM, Qu Tianlian wrote: Hi

Re: [HACKERS] [PATCHES] DELETE ... USING

Just to prevent a copy/paste error, I'd correct will no fail to will now fail in the suggested text below... -tfo -- Thomas F. O'Connell Co-Founder, Information Architect Sitening, LLC Strategic Open Source: Open Your i http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN

Re: [HACKERS] Views, views, views: Summary of Arguments

I guess I'm having difficulty understanding why the system catalogs themselves and provision of support for information_schema are not sufficient for what exists in core. At one point, there was a stored procedure database for Pl/PgSQL. It seems like a system view service like that could