any interaction with user.
It does not create any backward compatibility issues.
Not does it have any performance impact.
regards
bogdan
>From 450c339b4284887782b30e154766a0ee90d6f7ee Mon Sep 17 00:00:00 2001
From: Bogdan Pilch
Date: Sat, 16 Aug 2014 19:42:29 +0200
Subject: [PATCH 1/3] BPI: Ad
> On 9/29/14, 1:08 AM, Andres Freund wrote:
> >On 2014-09-28 20:32:30 -0400, Gregory Smith wrote:
> >>There are already a wide range of human readable time interval output
> >>formats available in the database; see the list at
> >>http://www.postgresql.org/docs/current/static/datatype-datetime.htm
How about, the format of psql duration can be set via some ...
backslash command or commdn line switch? And the default of course
remains the current behavior?
bogdan
> Andres Freund writes:
> > On 2014-09-28 20:32:30 -0400, Gregory Smith wrote:
> >> On 9/28/14, 7:49 AM,
s not create any backward compatibility issues as the default
behavior remains unchanged.
regards
bogdan
>From e3ba6cda83b64246c2b4d3df01f62444f4b37c9d Mon Sep 17 00:00:00 2001
From: Bogdan Pilch
Date: Sun, 7 Sep 2014 18:59:12 +0200
Subject: [PATCH] Implemented support for turning off/on tab co
issues if some SQL developers
assumed that the format is always ..
regards
bogdan
>From 25b2e3f9d888ecf0cc6fe0fbb569004cf9ce315b Mon Sep 17 00:00:00 2001
From: Bogdan Pilch
Date: Sat, 16 Aug 2014 23:20:18 +0200
Subject: [PATCH] BPI: Implemented enhancement f timing feature (displaying
time in a m