"Joachim Wieland" <[EMAIL PROTECTED]> writes:
> I thought however that it would be nice to offer a kind of regression
> framework, that lets you easily parse command line options, create a temp
> environment (if desired), initialize the server with databases, roles,
> languages, start up the server
Tom Lane wrote:
No, I guess I confused you by talking about the executor representation
at the same time. This is really unrelated to the executor. The join
tree I'm thinking of here is the data structure that dangles off
Query.jointree --- it's a representation of the query's FROM clause,
and
On Thu, 20 Jul 2006, Josh Berkus wrote:
> Peter,
>
> > I don't understand how that is related. Or what a conversion utility
> > would be for that matter.
>
> Well, the main issue with changing the units of the PostgreSQL.conf file
> from a user perspective is that the numbers from you 8.0/8.1 con
Hi Tom-san.
From: "Tom Lane" <[EMAIL PROTECTED]>
Log Message:
---
As a stopgap to get the Windows buildfarm members running again, hot-wire
the check on diff's exit status to check for literally 0 or 1. Someone
should look into why WIFEXITED/WEXITSTATUS don't work for this, but I've
s
Peter Eisentraut wrote:
Hannu Krosing wrote:
So we would have
src/pl/plphp/README.TXT
src/pl/pljava/README.TXT
src/pl/plj/README.TXT
and anybody looking for pl-s would find the info in a logical place
It could be interesting to have something like this:
./configure --with-plruby
and it wou
Joe Conway <[EMAIL PROTECTED]> writes:
> I'm liking this too. But when you say "jointree node", are you saying to
> model the new node type after NestLoop/MergeJoin/HashJoin nodes? These
> are referred to as "join nodes" in ExecInitNode. Or as you mentioned a
> couple of times, should this look
Tom Lane wrote:
Peter Eisentraut <[EMAIL PROTECTED]> writes:
And if that didn't convince you, I still got PL/sh in the wait ...
It seems like there may be enough interest in PL/Ruby to justify
including it in our distro, but after taking a look at the package
I can see a couple of pretty serio
Tom-san.
A...Sorry.
It looked for the optimal result.
===
All 100 tests passed.
===
However, A result tells a lie. So, pursuit continues tracking.
$ diff -w "./expected/char.out" "./results/char.out"
66d65
diff -w "./expected/char_1.out" "./result
Tom Lane wrote:
Joe Conway <[EMAIL PROTECTED]> writes:
I was actually just looking at that and ended up thinking that it might
be better to deal with it one level down in ExecProject (because it is
already passing targetlists directly to ExecTargetList).
I'd vote against that, because (a) Exe
On Thu, 2006-07-20 at 18:19 -0400, Tom Lane wrote:
> About the best bet is to make sure that's the *only* available index,
> and set enable_seqscan = off to be sure.
Another approach would be to define a UDF that takes a query string,
runs the parser, rewriter, and planner on the string and then c
Joshua Reich <[EMAIL PROTECTED]> writes:
> Is it safe to use the output of EXPLAIN in regression tests?
No, not unless you want the test to break every other week.
> I want to
> make sure that certain GiST indexes are being used by sample queries,
About the best bet is to make sure that's the
Peter Eisentraut wrote:
I think it would be useful to allow units to be added to these settings, for
example...
shared_buffers = 512MB
which is a bit cumbersome to calculate right now (you'd need = 65536).
I haven't thought yet how to parse or implement this, but would people find
this useful?
Is it safe to use the output of EXPLAIN in regression tests? I want to
make sure that certain GiST indexes are being used by sample queries,
but I am not sure if it is safe to rely on the format of EXPLAIN to be
unchanging.
Thoughts?
Josh Reich
---(end of broadcast)--
moises wrote:
Can any body talk me how many transactions make postgres in a second?
It depends on many things
1) speed of hardware/OS/number of disks/type of disks, if you use RAID
or not ...
2) number concurrent access
3) size of processed data in one transaction
4) database model
...
It n
This depends on your server capability and performance.. You
can use PostgreSQL as real time database. It is real not a toy :-)
Adnan DURSUNASRIN Bilisim Ltd.
Turkey
- Original Message -
From:
moises
To: pgsql-hackers@postgresql.org
Sent: Thursday,
Peter Eisentraut wrote:
Zdenek Kotala wrote:
Time units is easy:
1h = 60min = 3600s = 360ms
We don't need anything larger than seconds at the moment.
What kind of unit prefix will we use for memory?
PostgreSQL has always used 1 kB = 1024 B.
1) will be unit required?
No.
What will
Peter Eisentraut wrote:
One frequent source of confusion are the different units that the parameters
in postgresql.conf use. shared_buffers is in 8 kB, work_mem is in 1 kB;
bgwriter_delay is in milliseconds, checkpoint_warning is in seconds.
Obviously, we can't change that without inconvenien
On Thu, Jul 20, 2006 at 01:49:36PM +0200, Peter Eisentraut wrote:
> One frequent source of confusion are the different units that the parameters
> in postgresql.conf use. shared_buffers is in 8 kB, work_mem is in 1 kB;
> bgwriter_delay is in milliseconds, checkpoint_warning is in seconds.
> Ob
Reini Urban <[EMAIL PROTECTED]> writes:
> BTW: HAVE_LONG_LONG_INT_64 is defined, so INT64_IS_BUSTED is defined also.
You sure? INT64_IS_BUSTED should *not* be set in that case --- it's
only supposed to be set if we couldn't find any 64-bit-int type at all.
As for the regression test failure, it'
This is how netezza and teradata do it and it works very well.
In each of their cases you can see a graphical representation of the plan with
progress for each stage.
For the command line it would be great to just dump the current status, which
would provide a snapshot of the explain analyze.
On 7/14/2006 12:01 PM, Tom Lane wrote:
tsearch2 is functionality that definitely should be in core eventually,
but even Oleg still says it's not done. Aside from the documentation
issue, it's not clear that we've got a stable API for it.
Would moving it in its current state into core help it
Peter,
> I don't understand how that is related. Or what a conversion utility
> would be for that matter.
Well, the main issue with changing the units of the PostgreSQL.conf file
from a user perspective is that the numbers from you 8.0/8.1 conf file
would no longer work. A little conversion
Josh Berkus wrote:
> Well, the main issue with changing the units of the PostgreSQL.conf
> file from a user perspective is that the numbers from you 8.0/8.1
> conf file would no longer work.
No one is intending to do any such change.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
Josh Berkus wrote:
> Well, it's on my TODO list for 8.2 to write a simple postgresql.conf
> conversion utility in Perl. If you wanted to make a change like
> that, it would make finishing that mandatory.
I don't understand how that is related. Or what a conversion utility
would be for that mat
A couple months ago we were discussing partitioning the buffer mapping
table so as to reduce contention for the BufMappingLock. The discussion
stalled after I complained about the uncertainty of shared memory usage
arising from having a separate hashtable for each partition (since
different number
Can any body talk me how many transactions make
postgres in a second?
For example Inserts, Update, delete, etc.
I’m very interesting in this data, because I
want to use postgres for a real time database for process control.
Thanks and regards
___
Hello,
My Name is Moisés Herrera Vázquez, I begin to work
with PostgreSQL, for make a Real Data Base for Process Control.
I have some question for know what modules I have to
change for theses points
How can I Add some
kind of priorities to one transaction, for concurrency t
Zdenek Kotala wrote:
> Time units is easy:
> 1h = 60min = 3600s = 360ms
We don't need anything larger than seconds at the moment.
> What kind of unit prefix will we use for memory?
PostgreSQL has always used 1 kB = 1024 B.
> 1) will be unit required?
No.
> What will be default unit for va
Peter,
One frequent source of confusion are the different units that the parameters
in postgresql.conf use. shared_buffers is in 8 kB, work_mem is in 1 kB;
bgwriter_delay is in milliseconds, checkpoint_warning is in seconds.
Obviously, we can't change that without inconveniencing a lot of us
From: "Tom Lane"
> "Hiroshi Saito" <[EMAIL PROTECTED]> writes:
> > This is very strange.!!
> > boolean ... ok
> > char ... diff command failed with status 1: "diff -w
> > "./expected/char.out"
> > "./results/char.out" >"./results/char.diff""
> > server stopp
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
>>> 18% in s_lock is definitely bad :-(. Were you able to determine which
>>> LWLock(s) are accounting for the contention?
> Sorry for the delay. Finally I got the oprofile data. It's
> huge(34MB). If you are interested, I can put somewhere. Please let me
"Hiroshi Saito" <[EMAIL PROTECTED]> writes:
> This is very strange.!!
> boolean ... ok
> char ... diff command failed with status 1: "diff -w
> "./expected/char.out"
> "./results/char.out" >"./results/char.diff""
> server stopped
Yes, I believe the problem
OK, text again updated:
For schemas, allows access to objects contained in the specified
schema (assuming that the objects' own privilege requirements are
also met). Essentially this allows the grantee to look up
objects within the schema. Without this permission, it
On Thursday 20 July 2006 05:04, Jonah H. Harris wrote:
> On 7/20/06, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> > I think it would be useful to allow units to be added to these settings,
> > for example
> >
> > shared_buffers = 1000kB
> > checkpoint_warning = 30s
> >
> > This would also allow
>
Peter Eisentraut wrote:
One frequent source of confusion are the different units that the parameters
in postgresql.conf use. shared_buffers is in 8 kB, work_mem is in 1 kB;
bgwriter_delay is in milliseconds, checkpoint_warning is in seconds.
Obviously, we can't change that without inconvenien
On 7/20/06, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
One frequent source of confusion are the different units that the parameters
in postgresql.conf use. shared_buffers is in 8 kB, work_mem is in 1 kB;
bgwriter_delay is in milliseconds, checkpoint_warning is in seconds.
Obviously, we can't ch
On Thu, 20 Jul 2006, Peter Eisentraut wrote:
> One frequent source of confusion are the different units that the parameters
> in postgresql.conf use. shared_buffers is in 8 kB, work_mem is in 1 kB;
> bgwriter_delay is in milliseconds, checkpoint_warning is in seconds.
> Obviously, we can't change
On 7/20/06, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
I think it would be useful to allow units to be added to these settings, for
example
shared_buffers = 1000kB
checkpoint_warning = 30s
This would also allow
shared_buffers = 512MB
which is a bit cumbersome to calculate right now (you'd ne
One frequent source of confusion are the different units that the parameters
in postgresql.conf use. shared_buffers is in 8 kB, work_mem is in 1 kB;
bgwriter_delay is in milliseconds, checkpoint_warning is in seconds.
Obviously, we can't change that without inconveniencing a lot of users.
I t
"Jim C. Nasby" wrote:
> If you haven't changed checkpoint timeout, this drop-off every 4-6
> minutes indicates that you need to make the bgwriter more aggressive.
I'll say to a customer when proposing and explaining.
Thank you for the information.
Regards,
Katsuhiko Okano
okano katsuhiko
> > > If there is a work load tool of a free license, I would like to try.
> >
> >
> > FYI: there is a free tpc-w implementation done by Jan available at:
> > http://pgfoundry.org/projects/tpc-w-php/
>
> FYI(2):
>
> There is one more (pseudo) TPC-W implementation by OSDL.
>
>
> http://www
> We already have EXPLAIN ANALYZE. Perhaps the right way to do this is
> something that provides similar output. I could see something that
> looks like EXPLAIN for the parts that have not yet executed, something
> reasonable to show progress of the currently active part of the plan
> (current time
On 20/07/06, Reini Urban <[EMAIL PROTECTED]> wrote:
Thanks,
Which postgresql version?
The version is cvs HEAD.
Can we have a regular cygwin error report please mailed to cygwin at
cygwin.com please. See http://cygwin.com/problems.html (cygcheck -s -v
-r > cygcheck.out)
Looks like a strtod()
Adrian Maier schrieb:
Hello,
While setting up a buildfarm installation for cygwin, I've
uncountered the following
regression failure :
float8 ... FAILED
== pgsql.3132/src/test/regress/regression.diffs
*** ./expected/float8-small-is-zero.outTue Jul 18 09:2
44 matches
Mail list logo
