Gaetano Mendola <[EMAIL PROTECTED]> writes:
> Well, the unix guys have the abit to have the uptime as an interval, I'm
> inclined to have boths: pg_uptime ( interval ) and pg_starttime (
> timestamptz )
Well for the OS these are not redundant values. The clock could have been
adjusted at any t
This has been saved for the 8.1 release:
http:/momjian.postgresql.org/cgi-bin/pgpatches2
---
Simon Riggs wrote:
> On Sat, 2005-01-01 at 17:47, Simon Riggs wrote:
> > On Sat, 2005-01-01 at 17:01, Bruce Momjian wrote:
Peter Eisentraut wrote:
> Tom Lane wrote:
> > Pursuant to Theodore Petrosky's recent trouble report, I thought I
> > would see what happens if you try to build Postgres in a directory
> > whose path contains spaces,
>
> The last I heard in the autotools community on this issue was "forget
> it".
Did this get resolved as an OS file system issue?
---
Andrew Dunstan wrote:
>
>
> Tom Lane wrote:
>
> >Andrew Dunstan <[EMAIL PROTECTED]> writes:
> >
> >
> >>You're right - my query was not sufficiently specific. There
This item still seems open. Is it a TODO?
---
Hannu Krosing wrote:
> It seems that this bug is still lurking in libpq:
>
> http://search.postgresql.org/pgsql-hackers/2004-09/msg00703.php
>
> Is anybody working on it, or s
Matthias Schmidt wrote:
Hi Tom,
Am 31.12.2004 um 20:18 schrieb Tom Lane:
Matthias Schmidt <[EMAIL PROTECTED]> writes:
a) is the name uptime() OK?
Probably should use pg_uptime(), or something else starting with pg_.
What about 'pg_starttime()' since it is not a period but a point-in-time?
b) is
Simon Riggs wrote:
> Here's my bgwriter instrumentation patch, which gives info that could
> allow the bgwriter settings to be tuned.
Uh, what does this do exactly? Add additional logging output?
--
Bruce Momjian| http://candle.pha.pa.us
pgman@candle.pha.pa.us
On Mon, 2005-01-03 at 23:03, Bruce Momjian wrote:
> Simon Riggs wrote:
> > On Mon, 2005-01-03 at 20:09, Bruce Momjian wrote:
> > > OK, we have a submitted patch that attempts to improve bgwriter by
> > > making bgwriter_percent control what percentage of the buffer is
> > > scanned.
> > >
> > > Th
Simon Riggs wrote:
> On Mon, 2005-01-03 at 20:09, Bruce Momjian wrote:
> > OK, we have a submitted patch that attempts to improve bgwriter by
> > making bgwriter_percent control what percentage of the buffer is
> > scanned.
> >
> > The patch still needs doc changes and a change to the default valu
On Mon, 2005-01-03 at 20:09, Bruce Momjian wrote:
> OK, we have a submitted patch that attempts to improve bgwriter by
> making bgwriter_percent control what percentage of the buffer is
> scanned.
>
> The patch still needs doc changes and a change to the default value but
> at this point we need a
On Mon, 2005-01-03 at 17:14, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > The situation where another backend requests the block immediately
> > before the I/O is fairly common AFAICS, especially since
> > StrategyGetBuffer ignores the BM_DIRTY flag in selecting victims.
>
> How d
Jim Buttafuoco wrote:
> I also don't see MIPSEL and ARM on the list, both running debian
> sarge (in the build farm).
The mips entry is actually a mipsel, but uname identifies them the same.
I don't see any arm machine in the build farm.
--
Peter Eisentraut
http://developer.postgresql.org/~pet
On Mon, 3 Jan 2005, Bruce Momjian wrote:
OK, we have a submitted patch that attempts to improve bgwriter by
making bgwriter_percent control what percentage of the buffer is
scanned.
The patch still needs doc changes and a change to the default value but
at this point we need a vote on the patch. I
Tom Lane wrote:
> Pursuant to Theodore Petrosky's recent trouble report, I thought I
> would see what happens if you try to build Postgres in a directory
> whose path contains spaces,
The last I heard in the autotools community on this issue was "forget
it". Not that that means it's impossible,
I've uncovered a possible bug on that may be related to the other locale
relation issues for win32 being discussed right now. Basically, I have
a situation where a query is pulling up the wrong record based on string
case. So far, I have not been able to reproduce this in linux.
Here is the situ
Bruce Momjian writes:
> OK, we have a submitted patch that attempts to improve bgwriter by
> making bgwriter_percent control what percentage of the buffer is
> scanned.
> The patch still needs doc changes and a change to the default value but
> at this point we need a vote on the patch. Is it:
Hi All,
As part of my thesis I need to implement a new algorithm for
Full-Disjunctions and 2 older ones.
A short explanation of what Full-Disjunction is, is that it comes to
solve what A natural outer join
usually can't do when you have more than 2 relations.
The main goal is to retrieve maximal
I have not had time to test this.
cheers
andrew
Original Message
Subject:Re: postgres+tcl on cygwin
Date: Mon, 3 Jan 2005 03:50:24 -0800 (PST)
From: Patrick Samson <[EMAIL PROTECTED]>
To: Andrew Dunstan <[EMAIL PROTECTED]>
I succeeded in the build with the TCL sup
OK, we have a submitted patch that attempts to improve bgwriter by
making bgwriter_percent control what percentage of the buffer is
scanned.
The patch still needs doc changes and a change to the default value but
at this point we need a vote on the patch. Is it:
* too late for 8.0
Robert Treat wrote:
On Friday 31 December 2004 14:37, Joshua D. Drake wrote:
Hello,
Is there any reason why TSearch (not TSearch2) is still in
contrib? TSearch is a 7.3.x module...
I believe it was left in for backwards compatibility and afaik it still builds
in the 8.0 tree. If you'd like to mak
I wrote:
> I think that it would work for BufferAlloc to share-lock the victim
> buffer before calling FlushBuffer; we'd have to add a bool parameter to
> FlushBuffer telling it the lock was already acquired.
I've applied a patch for this.
> BTW, it looks to me like this deadlock potential has ex
Hello Marc,
Marc G. Fournier schrieb am 02.01.2005 15:56:
As was anticipated, time between Release Candidate 2 and 3 was nice and
short, with more changes being made now to Documentation vs Code.
A current list of *known* supported platforms can be found at:
http://developer.postgresql.org/su
Hi Tom,
Am 31.12.2004 um 20:18 schrieb Tom Lane:
Matthias Schmidt <[EMAIL PROTECTED]> writes:
a) is the name uptime() OK?
Probably should use pg_uptime(), or something else starting with pg_.
What about 'pg_starttime()' since it is not a period but a
point-in-time?
b) is the return-type 'Interva
Simon Riggs <[EMAIL PROTECTED]> writes:
> The situation where another backend requests the block immediately
> before the I/O is fairly common AFAICS, especially since
> StrategyGetBuffer ignores the BM_DIRTY flag in selecting victims.
How do you figure that? StrategyGetBuffer won't return the sa
Hi,
are there any plans for rewriting queries to preexisting materialized
views? I mean, rewrite a query (within the optimizer) to use a
materialized view instead of the originating table?
Regards,
Yann
---(end of broadcast)---
TIP 6: Have you sea
On Friday 31 December 2004 14:37, Joshua D. Drake wrote:
> Hello,
>
> Is there any reason why TSearch (not TSearch2) is still in
> contrib? TSearch is a 7.3.x module...
>
I believe it was left in for backwards compatibility and afaik it still builds
in the 8.0 tree. If you'd like to make the argu
I also don't see MIPSEL and ARM on the list, both running debian sarge (in the
build farm).
Jim
-- Original Message ---
From: Robert Treat <[EMAIL PROTECTED]>
To: pgsql-hackers@postgresql.org
Sent: 03 Jan 2005 08:35:19 -0500
Subject: Re: [HACKERS] [ANNOUNCE] PostgreSQL 8.0.0 Rel
On Sun, 2005-01-02 at 09:56, Marc G. Fournier wrote:
>
> As was anticipated, time between Release Candidate 2 and 3 was nice and
> short, with more changes being made now to Documentation vs Code.
>
> A current list of *known* supported platforms can be found at:
>
> http://developer.post
On Mon, 3 Jan 2005, Bruce Momjian wrote:
Tonight regular CVS is very slow to generate a diff. Does anyone know
why? Load average is only 2.0.
if load avg is that low, then I'd have to say there is some network lag
somewhere ... if load avg was higher, then I'd say a flood of messages to
majordo
Thanks!
Your advice helped me find what caused the problem immediately. It was a
wrong 'palloc' as you suspected (and as usual for me ;-) ).
Ntinos Katsaros
Tom Lane writes:
[EMAIL PROTECTED] writes:
While writting some code for the backend (some SPI-like functions for a
project) I saw this
30 matches
Mail list logo
