Tom Lane escribió:
> Actually, \a and \H are fairly bogus anyway, because they are "toggling"
> a setting that has more than two values. I wonder whether defining the
> argument as a boolean is really very sane. Perhaps it would be better to
> take the argument if given as just a regular format
David Fetter <[EMAIL PROTECTED]> writes:
> On Tue, May 13, 2008 at 11:36:57AM -0400, Tom Lane wrote:
>>> Uh, my point was that the agreement was to do this to *all* of
>>> psql's toggling backslash commands, not only \timing.
>>
>> Done :)
Hmm, I thought we had a lot more than three that were lik
On Tue, May 13, 2008 at 01:53:33PM -0700, David Fetter wrote:
> On Tue, May 13, 2008 at 11:36:57AM -0400, Tom Lane wrote:
> > David Fetter <[EMAIL PROTECTED]> writes:
> > >>> Surely this is merely proof of concept and not a complete patch.
> > >>
> > >> Next patch attached :)
> >
> > Uh, my point
On Tue, May 13, 2008 at 11:36:57AM -0400, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> >>> Surely this is merely proof of concept and not a complete patch.
> >>
> >> Next patch attached :)
>
> Uh, my point was that the agreement was to do this to *all* of
> psql's toggling backsla
David Fetter <[EMAIL PROTECTED]> writes:
>>> Surely this is merely proof of concept and not a complete patch.
>>
>> Next patch attached :)
Uh, my point was that the agreement was to do this to *all* of psql's
toggling backslash commands, not only \timing.
regards, tom lan
On Tue, May 13, 2008 at 08:14:51AM -0700, David Fetter wrote:
> On Tue, May 13, 2008 at 10:47:40AM -0400, Alvaro Herrera wrote:
> > Tom Lane escribió:
> > > Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > > > David Fetter escribi?:
> > > >> Thanks for the heads-up :)
> > > >>
> > > >> Second patch
On Tue, May 13, 2008 at 10:47:40AM -0400, Alvaro Herrera wrote:
> Tom Lane escribió:
> > Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > > David Fetter escribi?:
> > >> Thanks for the heads-up :)
> > >>
> > >> Second patch attached, this time with some docs.
> >
> > > Added to July commitfest.
> >
Tom Lane escribió:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > David Fetter escribi�:
> >> Thanks for the heads-up :)
> >>
> >> Second patch attached, this time with some docs.
>
> > Added to July commitfest.
>
> Surely this is merely proof of concept and not a complete patch.
David, ya he
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> David Fetter escribió:
>> Thanks for the heads-up :)
>>
>> Second patch attached, this time with some docs.
> Added to July commitfest.
Surely this is merely proof of concept and not a complete patch.
regards, tom lane
--
Se
David Fetter escribió:
> Thanks for the heads-up :)
>
> Second patch attached, this time with some docs.
Added to July commitfest.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
--
Sent via p
On Mon, May 12, 2008 at 05:30:48PM -0400, Bruce Momjian wrote:
> David Fetter wrote:
> > On Sun, May 11, 2008 at 11:48:29PM -0400, Tom Lane wrote:
> > > "Scott Marlowe" <[EMAIL PROTECTED]> writes:
> > > > Is it reasonable behavior to have \timing along toggle and \timing on
> > > > / \timing off be
David Fetter escribió:
> On Sun, May 11, 2008 at 11:48:29PM -0400, Tom Lane wrote:
> > "Scott Marlowe" <[EMAIL PROTECTED]> writes:
> > > Is it reasonable behavior to have \timing along toggle and \timing on
> > > / \timing off be a forced switch? Just thinking of other scripts
> > > where this isn
David Fetter wrote:
> On Sun, May 11, 2008 at 11:48:29PM -0400, Tom Lane wrote:
> > "Scott Marlowe" <[EMAIL PROTECTED]> writes:
> > > Is it reasonable behavior to have \timing along toggle and \timing on
> > > / \timing off be a forced switch? Just thinking of other scripts
> > > where this isn't
On Sun, May 11, 2008 at 11:48:29PM -0400, Tom Lane wrote:
> "Scott Marlowe" <[EMAIL PROTECTED]> writes:
> > Is it reasonable behavior to have \timing along toggle and \timing on
> > / \timing off be a forced switch? Just thinking of other scripts
> > where this isn't a problem and having to update
"Scott Marlowe" <[EMAIL PROTECTED]> writes:
> Is it reasonable behavior to have \timing along toggle and \timing on
> / \timing off be a forced switch? Just thinking of other scripts
> where this isn't a problem and having to update them.
The command without an argument should certainly keep the
On Sun, May 11, 2008 at 9:04 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> Francisco Reyes <[EMAIL PROTECTED]> writes:
>> Tom Lane writes:
>>> Not that I know of :-(. There's been discussion of fixing all of psql's
>>> "toggle" commands to offer "\foo on" and "\foo off"
>
>> What would be a good start
Francisco Reyes <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> Not that I know of :-(. There's been discussion of fixing all of psql's
>> "toggle" commands to offer "\foo on" and "\foo off"
> What would be a good starting point for someone interesting in looking into
> working on that?
This'
Tom Lane writes:
Not that I know of :-(. There's been discussion of fixing all of psql's
"toggle" commands to offer "\foo on" and "\foo off"
What would be a good starting point for someone interesting in looking into
working on that?
Started a job recently as PostgresSQL DBA.. so sooner or
Francisco Reyes <[EMAIL PROTECTED]> writes:
> Is there a way to make certain \timing is on?
Not that I know of :-(. There's been discussion of fixing all of psql's
"toggle" commands to offer "\foo on" and "\foo off" variants, which
would be far more scripting-friendly ... but nobody's stepped up
Is there a way to make certain \timing is on?
I am looking for something simmilar to what one can do with the pager
\pset pager always
Most scripts I am working with (inheritted) don't have \timing in them so I
can put timing on/off as needed. However some scripts already have it. So if
I set
... this one works as expected too ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
21 matches
Mail list logo
