--On Monday, November 03, 2003 00:36:41 -0600 Larry Rosenman
<[EMAIL PROTECTED]> wrote:
We pass all tests except for the Join test now. the join test seems to
just be row-ordering from qsort():
test union... ok
test case ... ok
test join ... FAIL
We pass all tests except for the Join test now. the join test seems to
just be row-ordering from qsort():
test union... ok
test case ... ok
test join ... FAILED
test aggregates ... ok
===
1 of 93 tests failed.
On Mon, 2003-11-03 at 01:07, Neil Conway wrote:
> (1) As Manfred originally noted, when we advance to a new XLOG segment,
> we can use POSIX_FADV_DONTNEED to let the kernel know we won't be
> accessing the old WAL segment anymore. I've attached a quick kludge of a
> patch that implements this. I ha
--On Monday, November 03, 2003 01:38:54 -0400 "Marc G. Fournier"
<[EMAIL PROTECTED]> wrote:
As Tom announced on Friday, Release Candidate 1 has now been tag'd and
bundled ... please test to confirm that nothing seems off with this build
...
I'm going to do a broader announce on it tonight, to t
A couple days ago, Manfred Spraul mentioned the posix_fadvise() API on
-hackers:
http://www.opengroup.org/onlinepubs/007904975/functions/posix_fadvise.html
I'm working on making use of posix_fadvise() where appropriate. I can
think of the following places where this would be useful:
(1) As Manfr
As Tom announced on Friday, Release Candidate 1 has now been tag'd and
bundled ... please test to confirm that nothing seems off with this build
...
I'm going to do a broader announce on it tonight, to the -announce and
-general lists ...
Also, I've created a branch (REL7_4_STABLE) so that work
Fabrizio Mazzoni wrote:
Hello all .. i just wrote this script in plpgsql. Basically it
performs a crosstab query. The difference between this and the one
you already have in contrib is that this one has no limitations on
the arguments passed to it.
I don't understand what you think is different. Yo
Tom Lane wrote:
Attached is an extremely crude prototype patch for making VACUUM delay
by a configurable amount between pages, in hopes of throttling its disk
bandwidth consumption. By default, there is no delay (so no change in
behavior). In some quick testing, setting vacuum_page_delay to 10
(m
Centuries ago, Nostradamus foresaw when "Stephen" <[EMAIL PROTECTED]> would write:
> As it turns out. With vacuum_page_delay = 0, VACUUM took 1m20s (80s)
> to complete, with vacuum_page_delay = 1 and vacuum_page_delay = 10,
> both VACUUMs completed in 18m3s (1080 sec). A factor of 13 times!
> This
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> I've tried PG 7.4 on a PlayStation 2/Linux. This is a kind of mips
> machine but apparently doesn't like the existing mips assembly code
> (illegal instruction errors).
Yes, that was known already --- apparently it uses a variant MIPS chip
with no sp
Hello all .. i just wrote this script in plpgsql. Basically it performs a crosstab
query. The difference between this and the one you already have in contrib is that
this one has no limitations on the arguments passed to it. The headers of the
resulting query are passed as a csv string so it can
Tom Lane kirjutas P, 02.11.2003 kell 20:00:
> Jan Wieck <[EMAIL PROTECTED]> writes:
> > I am currently looking at implementing ARC as a replacement strategy. I
> > don't have anything that works yet, so I can't really tell what the
> > result would be and it might turn out that we want both featu
Manfred Spraul <[EMAIL PROTECTED]> writes:
> If I understand libpq sources correctly, the first packets are send
> during connection setup - PQsigpipeOK(PGconn *) would be too late.
> That's why I added "sigpipe=caller" as a new flag for PQconnectdb.
That's definitely a problem, but "sigpipe=call
Hello all .. i just wrote this script in plpgsql. Basically it performs a crosstab
query. The difference between this and the one you already have in contrib is that
this one has no limitations on the arguments passed to it. The headers of the
resulting query are passed as a csv string so it can
I've tried PG 7.4 on a PlayStation 2/Linux. This is a kind of mips
machine but apparently doesn't like the existing mips assembly code
(illegal instruction errors). I've also tried --disable-spinlocks to turn
off the use of the assembly code, without success.
The old report from 7.3 has the comm
Not surprising, I should have thought. Why would you care that much?
The idea as I understand it is to improve the responsiveness of things
happening alongside vacuum ("real work"). I normally run vacuum when I
don't expect anything else much to be happening - but I don't care how
long it take
AgentM wrote:
That wouldn't offer a solution for people who use SIGPIPE for other
things during the lifetime of the program (after creating the
connection) and if a SIGPIPE handler is called due to the connection,
the handler won't be expecting the source, and polling signal for
state is essen
As it turns out. With vacuum_page_delay = 0, VACUUM took 1m20s (80s) to
complete, with vacuum_page_delay = 1 and vacuum_page_delay = 10, both
VACUUMs completed in 18m3s (1080 sec). A factor of 13 times! This is for a
single 350 MB table.
Apparently, it looks like the upcoming Linux kernel 2.6 will
--- Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> Michael Mauger writes:
>
> > I'm the maintainer of sql.el in GNU Emacs. On both the Mac OS X
> > and the Windows/Cygwin platform we've had reports that psql run
> > under Emacs does not issue a prompt for commands.
>
> Why can't you make the Emac
--- Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> Michael Mauger writes:
>
> > Emacs is not a Cygwin (Un*x emulation on Windows) executable (like
> > psql is)
>
> Why don't you use the native Windows version of psql?
>
The Cygwin setup program makes pre-built binaries of postgres readily
availa
This is my first time posting and I' hope I'm posting in the correct place. I hope
this is not an old topic I'm bringing to light...
It would be nice if when getting an error like: ERROR: Bad boolean external
representation ''
(or the like)...it would give a column name where that error was
On Sunday, Nov 2, 2003, at 18:16 Europe/Berlin, Tom Lane wrote:
Manfred Spraul <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
I don't see that this proposal adds any security.
It's not about security:
The proposal would be more salable if it addressed the security problem
too. As is, you are proposi
Jan Wieck <[EMAIL PROTECTED]> writes:
> I am currently looking at implementing ARC as a replacement strategy. I
> don't have anything that works yet, so I can't really tell what the
> result would be and it might turn out that we want both features.
It's likely that we would. As someone (you?)
Manfred Spraul <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I don't see that this proposal adds any security.
>>
> It's not about security:
The proposal would be more salable if it addressed the security problem
too. As is, you are proposing putting a large wart on libpq's API in
order to wo
Markus Bertheau writes:
> It seems to me that the TODO item under Clients
>
> * -Allow psql to do table completion for SELECT * FROM schema_part and
> table completion for SELECT * FROM schema_name.
>
> Is already implemented.
That's why there is a dash in front of it.
--
Peter Eisentraut [
Hi,
It seems to me that the TODO item under Clients
* -Allow psql to do table completion for SELECT * FROM schema_part and
table completion for SELECT * FROM schema_name.
Is already implemented. If not what does it mean?
select * from sche
completes the schema, and
select * from schema_a.ta
On Sat, 2003-11-01 at 20:58, Mark Wong wrote:
> I don't remember making a conscious decision between the number and integer
> database type. Is that a significant oversight on my part?
Numerics do exact math with support for arbitrary numbers. Unlike
Oracle, PostgreSQL does not retype NUMBER to
Mark Wong wrote:
On Sat, Nov 01, 2003 at 10:29:34PM +0100, Manfred Spraul wrote:
Mark Wong wrote:
Yeah, my dbt2 applications are multithreaded.
Do you need SIGPIPE delivery in your app? If no, could you try what
happens if you apply the attached patch to postgres, and perform the
Christopher Kings-Lynne writes:
> Have we implemented a bunch of those Array features now?
No, see http://archives.postgresql.org/pgsql-hackers/2003-06/msg01167.php
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 8: explain
Has anyone looked at this yet?
http://developer.postgresql.org/docs/postgres/unsupported-features-sql99.html
Have we implemented a bunch of those Array features now?
Chris
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choo
30 matches
Mail list logo
