Bruce Momjian pgman@candle.pha.pa.us writes:
I think we should return intervals only when we can't return meaningful
timestamp values. I don't have any logic to back up that opinion, though.
It's easy: a value measured as an interval will be obsolete by the time
it's delivered to the client. A
This has been saved for the 8.1 release:
http://momjian.postgresql.org/cgi-bin/pgpatches2
---
Euler Taveira de Oliveira wrote:
Bruce Momjian wrote:
This has been saved for the 8.1 release:
Bruce Momjian wrote:
This has been saved for the 8.1 release:
http:/momjian.postgresql.org/cgi-bin/pgpatches2
---
Hi,
I redo this patch adding the funcionality that Matthias implemented
(starttime).
This has been saved for the 8.1 release:
http:/momjian.postgresql.org/cgi-bin/pgpatches2
---
Euler Taveira de Oliveira wrote:
Hi,
This patch just implement a function that returns the uptime of
the
Hi,
This patch just implement a function that returns the uptime of
the
postmaster.
Doesn't work in EXEC_BACKEND case.
Sorry. I'll fix this.
Patch updated. I improved the function output too.
Comments?
=
Euler Taveira de Oliveira
euler[at]yahoo_com_br
On Wed, Dec 22, 2004 at 12:57:34AM -0300, Euler Taveira de Oliveira wrote:
Hi,
Patch updated. I improved the function output too.
Is it really a good idea to have a new file for only one function?
We regularly see complaints about not wanting to do basic source code
cleanup because not wanting
Hi Alvaro,
Patch updated. I improved the function output too.
Is it really a good idea to have a new file for only one function?
We regularly see complaints about not wanting to do basic source code
cleanup because not wanting to disrupt CVS history ...
I couldn't see a good place to
Euler Taveira de Oliveira [EMAIL PROTECTED] writes:
This patch just implement a function that returns the uptime of the
postmaster.
Doesn't work in EXEC_BACKEND case.
regards, tom lane
---(end of broadcast)---
TIP 1:
