On Mon, 2004-12-20 at 01:17, Mark Kirkwood wrote:
Mark Kirkwood wrote:
It occurs to me that cranking up the number of transactions (say
1000-10) and seeing if said regression persists would be
interesting. This would give the smoothing effect of the bgwriter
(plus the ARC) a
On Mon, 2004-12-20 at 06:34, Jim C. Nasby wrote:
On Sun, Dec 19, 2004 at 11:35:02PM +0200, Heikki Linnakangas wrote:
On Sun, 19 Dec 2004, Tom Lane wrote:
Heikki Linnakangas [EMAIL PROTECTED] writes:
On Sun, 19 Dec 2004, Alvaro Herrera wrote:
This is not useful at all, because the
On Thu, 2004-12-16 at 17:54, Richard Huxton wrote:
Josh Berkus wrote:
Clearly, OSDL-DBT2 is not a real world test! That is its benefit, since
it is heavily instrumented and we are able to re-run it many times
without different parameter settings. The application is well known and
doesn't
On Thu, 2004-12-16 at 11:07, Neil Conway wrote:
Zeugswetter Andreas DAZ SD wrote:
This has the disadvantage of converging against 0 dirty pages.
A system that has less than maxpages dirty will write every page with
every bgwriter run.
Yeah, I'm concerned about the bgwriter being overly
Sibtay Abbas wrote:
what is the value of yyin variable for postgresql
parser.
We don't use yyin. See scanner_init() in src/backend/parser/scan.l
about the scanner initialization.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of
Tom Lane wrote:
Gaetano Mendola [EMAIL PROTECTED] writes:
I'm having a bounce of errors because IMMUTABLE and STABLE
attributes for some of my functions. Let me explain with an example,
Hmm. This particular example is a bug in exec_eval_simple_expr() ...
if we're going to bypass SPI then we'd
On R, 2004-12-17 at 21:12, Thomas Hallgren wrote:
I'd like some views on the following issue.
The pljava function call handler will resolve a class name using a
loader that in turn uses a specific table in the PostgreSQL database.
Hence, the caller of the function must have select
Hannu Krosing wrote:
Would SECURITY DEFINER not work for pljava ?
Or if you are looking for something that has to be done inside the pl
handler maybe you should use another function with SECURITY DEFINER and
owned by superuser for function lookups ?
Of course. That's even better then a SetUser.
On Mon, Dec 20, 2004 at 06:23:24PM +1100, Gavin Sherry wrote:
On Sat, 18 Dec 2004, Bruce Momjian wrote:
Agreed. Once concern I have about allowing the lock table to spill to
disk is that a large number of FOR UPDATE locks could push out lock
entries used by other backends, causing very
Gavin Sherry [EMAIL PROTECTED] writes:
I think if we allow the lock manager to spill to disk (and I think we do
need to allow it) then we should also be able to control the amount of
shared memory allocated.
You mean like max_locks_per_transaction?
regards, tom lane
Alvaro Herrera [EMAIL PROTECTED] writes:
Gavin also mentioned to me we should also control the amount of memory
the shared inval queue uses.
Perhaps, but I've really seen no evidence that there's a need to worry
about that. Without demonstrated problems I'd sooner keep that code a
bit simpler
overbored [EMAIL PROTECTED] writes:
Hi all, I added a new variable-length field to the pg_class catalog, but
I did something wrong, and I can't tell what else I'd need to change.
...
The REVOKE command invokes ExecuteGrantStmt_Relation() to modify the
relacl attribute of pg_class, which is
Tom lane wrote:
Gavin Sherry [EMAIL PROTECTED] writes:
I think if we allow the lock manager to spill to disk (and I think
we do
need to allow it) then we should also be able to control the amount
of
shared memory allocated.
You mean like max_locks_per_transaction?
IMO,
Merlin Moncure [EMAIL PROTECTED] writes:
I may be over my head here, but I think lock spillover is dangerous. In
the extreme situations where this would happen, it would be a real
performance buster. Personally, I would rather see locks escalate when
the table gets full, or at least allow
Hi everyone,
From the TODO items:
Use index to restrict rows returned by multi-key index
when used with non-consecutive keys to reduce heap
accesses.
For an index on col1,col2,col3, and a WHERE clause of
col1 = 5 and col3 = 9, spin though the index checking
for col1 and col3 matches, rather than
Jaime Casanova wrote:
Hi everyone,
From the TODO items:
Use index to restrict rows returned by multi-key index
when used with non-consecutive keys to reduce heap
accesses.
For an index on col1,col2,col3, and a WHERE clause of
col1 = 5 and col3 = 9, spin though the index checking
for col1
On Mon, Dec 20, 2004 at 11:47:41AM -0500, Tom Lane wrote:
To me, performance buster is better than random, unrepeatable
deadlock failures. In any case, if we find we *can't* implement this
in a non-performance-busting way, then it would be time enough to look
at alternatives that force the
On Mon, Dec 20, 2004 at 11:58:21AM -0600, Jaime Casanova wrote:
Jaime,
I was looking in the archives something about this but
i found nothing. Where can i found the thread (i
suppose should be one) about this issue?
Did you use the search engine at http://www.pgsql.ru ?
--
Alvaro Herrera
Alvaro Herrera [EMAIL PROTECTED] writes:
To solve the problem I want to solve, we have three orthogonal
possibilities:
1. implement shared row locking using the ideas outlined in the mail
starting this thread (pg_clog-like seems to be the winner, details TBD).
2. implement shared lock table
Barring loud squawks, Marc will bundle up 8.0RC2 this evening sometime.
Anybody got last-minute stuff?
regards, tom lane
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
On Mon, Dec 20, 2004 at 02:04:46PM -0500, Tom Lane wrote:
Barring loud squawks, Marc will bundle up 8.0RC2 this evening sometime.
Anybody got last-minute stuff?
Is the following a plperl problem or does it need to be fixed in
DBD::PgSPI? I never saw any responses.
Michael Fuhr [EMAIL PROTECTED] writes:
Is the following a plperl problem or does it need to be fixed in
DBD::PgSPI? I never saw any responses.
http://archives.postgresql.org/pgsql-bugs/2004-12/msg00097.php
AFAIK it's a PgSPI issue. plperl wraps its spi.c calls in a
subtransaction, but it
Tom Lane [EMAIL PROTECTED] wrote on 20.12.2004, 19:34:21:
Alvaro Herrera writes:
To solve the problem I want to solve, we have three orthogonal
possibilities:
1. implement shared row locking using the ideas outlined in the mail
starting this thread (pg_clog-like seems to be the
8.0.0rc1 builds and passes 'make check' on Gentoo Linux (amd64) with the
dependencies I have to hand (no tcl or kerberos):
$ ./configure --prefix=/home/oliver/pg/8.0.0rc1 --with-pgport=5800
-enable-thread-safety --with-perl --with-python --with-pam -with-openssl
$ uname -a
Linux extrashiny
Tom Lane said:
Barring loud squawks, Marc will bundle up 8.0RC2 this evening sometime.
Anybody got last-minute stuff?
I have not been able to build Cygwin with pltcl, and neither has anyone else
to the best of my knowledge.
I will investigate - probably a makefile issue - unless someone else
Goal: on a prduction server, to gradually shrink a table (no matter how
large) back to 10% free space without noticeably interrupting write
access to it. (noticeably = without taking any exclusive locks for
more than a few seconds at a time.)
I am thinking about making this if it proves to
Andrew Dunstan [EMAIL PROTECTED] writes:
Anybody got last-minute stuff?
I have not been able to build Cygwin with pltcl, and neither has anyone else
to the best of my knowledge.
Has that worked in prior releases?
regards, tom lane
---(end of
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Anybody got last-minute stuff?
I have not been able to build Cygwin with pltcl, and neither has anyone else
to the best of my knowledge.
Has that worked in prior releases?
I have no idea. It's hard to think of a reason
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
I have not been able to build Cygwin with pltcl, and neither has anyone else
to the best of my knowledge.
Has that worked in prior releases?
I have no idea. It's hard to think of a reason in
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane wrote:
Nope. What are the symptoms exactly?
log attached. Looks like there is at least a missing -ltcl in the call
to dllwrap, but that's not all.
Agreed on missing -ltcl. It seems odd given that the Cygwin case in
Makefile.shlib does
Both added to TODO:
---
Simon Riggs wrote:
On Mon, 2004-11-29 at 13:10, Bruce Momjian wrote:
Or TODO maybe worded as:
* Allow the PITR process to be debugged and data examined
Yes, thats good for me...
We are now packaging RC2. If nothing comes up after RC2 is released, we
can move to final release.
The open items list is attached. The doc changes can be easily
completed before final. The only code issue left is with bgwriter. We
always knew we needed to find better defaults for its
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane wrote:
Agreed on missing -ltcl. It seems odd given that the Cygwin case in
Makefile.shlib does include $(SHLIB_LINK) and pltcl's Makefile does add
$(TCL_LIB_SPEC) to SHLIB_LINK. Is TCL_LIB_SPEC getting set reasonably
by configure?
$ grep
Tom Lane wrote:
here's what is in /usr/lib/tclConfig.sh - maybe there's a clue in there
- or maybe it's just a problem with the Cygwin-supplied package - I have
deliberately not tried to fix this by installing my own build of tcl.
The Cygwin-supplied package is evidently broken beyond
Bruce Momjian [EMAIL PROTECTED] writes:
I think the ideal solution would be to remove bgwriter_percent or change
it to be a percentage of all buffers, not just dirty buffers, so we
don't have to scan the entire list. If we set the new value to 10% with
a delay of 1 second, and the bgwriter
Andrew Dunstan [EMAIL PROTECTED] writes:
I am abandoning further effort altogether, because of this:
adunstan: ~/tcl8.4.9/win
$ ./configure --enable-shared
checking for Cygwin environment... yes
configure: error: Compiling under Cygwin is not currently supported.
A maintainer for the Cygwin
On Tue, 14 Dec 2004, Peter Eisentraut wrote:
Am Samstag, 4. Dezember 2004 00:12 schrieb Marc G. Fournier:
look her over ... I forced a sync to the ftp.postgresql.org server, so its
available there ... will announce later this evening baring any 'its
broken' commends ;)
You are building the
At 2004-12-19 17:56:00 +0530, [EMAIL PROTECTED] wrote:
I've asked the Ethereal people if they want to distribute this with
Ethereal.
It's in Ethereal CVS now.
-- ams
---(end of broadcast)---
TIP 2: you can get off all lists at once with the
Ok,
I didn't think you could do a restore as a non-superuser. I had
executed the command on the remote(cygwin) machine in this case. I
didn't specify a user to have it run as on the windows side (thought it
would default to postgres).
On the cygwin side I did execute it under a non-superuser
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
I think the ideal solution would be to remove bgwriter_percent or change
it to be a percentage of all buffers, not just dirty buffers, so we
don't have to scan the entire list. If we set the new value to 10% with
a delay of 1
Marc G. Fournier wrote:
On Tue, 14 Dec 2004, Peter Eisentraut wrote:
Am Samstag, 4. Dezember 2004 00:12 schrieb Marc G. Fournier:
look her over ... I forced a sync to the ftp.postgresql.org server, so its
available there ... will announce later this evening baring any 'its
broken'
On Mon, 20 Dec 2004, Bruce Momjian wrote:
Marc G. Fournier wrote:
On Tue, 14 Dec 2004, Peter Eisentraut wrote:
Am Samstag, 4. Dezember 2004 00:12 schrieb Marc G. Fournier:
look her over ... I forced a sync to the ftp.postgresql.org server, so its
available there ... will announce later this
Bruce Momjian [EMAIL PROTECTED] writes:
You need a clock sweep like BSD uses (and probably others).
No, that's *fundamentally* wrong.
The reason we are going to the trouble of maintaining a complicated
cache algorithm like ARC is so that we can tell the heavily used pages
from the lesser used
Bruce Momjian [EMAIL PROTECTED] writes:
I am confused. If we change the percentage to be X% of the entire
buffer cache, and we set it to 1%, and we exit when either the dirty
pages or % are reached, don't we end up just scanning the first 1% of
the cache over and over again?
Exactly. But 1%
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
I am confused. If we change the percentage to be X% of the entire
buffer cache, and we set it to 1%, and we exit when either the dirty
pages or % are reached, don't we end up just scanning the first 1% of
the cache over and over
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
Exactly. But 1% would be uselessly small with this definition. Offhand
I'd think something like 50% might be a starting point; maybe even more.
What that says is that a page isn't a candidate to be written out by the
bgwriter until
Hi
I have a few people in Europe trying out the rc1 port for OS/2 and they
have run into a problem with the locale settings
They have a locale set as de_DE_EURO and the initdb program really does
not like this because the setlocale(LC_MESSAGES, NULL) call returns a zero
length string. When the
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
Exactly. But 1% would be uselessly small with this definition. Offhand
I'd think something like 50% might be a starting point; maybe even more.
What that says is that a page isn't a candidate to be written out by
On Mon, 20 Dec 2004, Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
Exactly. But 1% would be uselessly small with this definition. Offhand
I'd think something like 50% might be a starting point; maybe even more.
What that says is that a page isn't a candidate
Gavin Sherry wrote:
Neil and I spoke with Jan briefly last week and he mentioned a few
different approaches he'd been tossing over. Firstly, for alternative
runs, start X% on from the LRU, so that we aren't scanning clean buffers
all the time. Secondly, follow something like the approach
Le 16 déc. 04, à 22:48, Bruce Momjian a écrit :
I am confused by the threading failure. I don't see any free() call in
thread_test.c. Would you go to the tools/thread directory and run the
program manually and use a debugger to see the failure line? Is there
some threading flag NetBSD requires
Respected Sir
This is srinvas.
I have been working with Postgresql and have
created tables,constraints and so on.
Now i am writing stored functions using refcursor
and the stored function havecreated successfully. But i have problem to
validate the parameters passed in the call function..
Postgresql-8.0.0rc1
hardware: HP Dual PPro
os: Linux Slackware 10.0.0
kernel: 2.6.9-ac16 SMP
gcc: 3.3.4
configure: ./configure --prefix=/usr/local/pgsql --with-tcl --with-perl
--with-x --enable-syslog --with-openssl --with-pgport=5432 --with-odbc
--enable-thread-safety
8.0.0beta4 was
check her over ..
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664
---(end of broadcast)---
TIP 9: the planner will ignore your desire to
Will do...
thanks
Lorne
In [EMAIL PROTECTED], on 12/21/04
at 01:56 AM, Marc G. Fournier [EMAIL PROTECTED] said:
check her over ..
Marc G. Fournier Hub.Org Networking Services
(http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy
ICQ:
Gavin Sherry [EMAIL PROTECTED] writes:
I was also thinking of benchmarking the effect of changing the algorithm
in StrategyDirtyBufferList(): currently, for each iteration of the loop we
read a buffer from each of T1 and T2. I was wondering what effect reading
T1 first then T2 and vice versa
[EMAIL PROTECTED] writes:
I have a few people in Europe trying out the rc1 port for OS/2 and they
have run into a problem with the locale settings
They have a locale set as de_DE_EURO and the initdb program really does
not like this because the setlocale(LC_MESSAGES, NULL) call returns a zero
57 matches
Mail list logo
