I would like some configuration parameters to Pl/Java and I would like some
advice. Where should they go?
1. Something similar to postgresql.conf (it's not extendable though, is it?)
2. A Table in the database in the sqlj schema
3. Java properties file (cumbersome, must be available prior to
Am Freitag, 6. Februar 2004 10:27 schrieb Thomas Hallgren:
I would like some configuration parameters to Pl/Java and I would like some
advice. Where should they go?
1. Something similar to postgresql.conf (it's not extendable though, is
it?)
No, it is not.
2. A Table in the database in the
Peter Eisentraut [EMAIL PROTECTED] writes:
Am Freitag, 6. Februar 2004 10:27 schrieb Thomas Hallgren:
I would like some configuration parameters to Pl/Java and I would like some
advice. Where should they go?
1. Something similar to postgresql.conf (it's not extendable though, is
it?)
No,
Tom Lane wrote:
Zeugswetter Andreas SB SD [EMAIL PROTECTED] writes:
So Imho the target should be to have not much IO open for the checkpoint,
so the fsync is fast enough, even if serial.
The best we can do is push out dirty pages with write() via the bgwriter
and hope that the kernel will see
Joe Conway [EMAIL PROTECTED] writes:
I still think it is a good idea and that
the difficulties can be worked out.
What do you think of the idea of suppressing the unknown variable
error for some class of variable names?
If we had agreement on doing that then I think the rest would be pretty
[ moving to HACKERS ]
Mark Gibson wrote:
Joe Conway wrote:
Mark Gibson wrote:
[custom datatype oid mismatch between local and remote side of
dblink ]
Without actually having tried it, I think you could hack
pgresultGetTupleDesc() in dblink.c. Replace the line: atttypid =
PQftype(res, i); with an
Tom Lane wrote:
Peter Eisentraut [EMAIL PROTECTED] writes:
Am Freitag, 6. Februar 2004 10:27 schrieb Thomas Hallgren:
1. Something similar to postgresql.conf (it's not extendable though, is
it?)
No, it is not.
In principle it could be --- the mechanisms already exist in guc.c to
permit outside
Tom Lane wrote:
What do you think of the idea of suppressing the unknown variable
error for some class of variable names?
I like it. I wonder if we ought to have a way to register valid
classes? Maybe a new guc variable in the form of a list of valid
classes. So something like:
Joe Conway [EMAIL PROTECTED] writes:
I like it. I wonder if we ought to have a way to register valid
classes? Maybe a new guc variable in the form of a list of valid
classes. So something like:
There are some order-of-processing issues there, but maybe. Another
possibility is that after a
On 5 Jan, Tom Lane wrote:
Josh Berkus [EMAIL PROTECTED] writes:
2) DEVELOP BETTER PLANS FOR OR GROUP QUERIES
Summary: Currently, queries with complex or group criteria get devolved by
the planner into canonical and-or filters resulting in very poor execution on
large data sets. We
[EMAIL PROTECTED] writes:
Sorry it's taking so long. I tried to take a export from CVS today and
the database appears not to be able to connect to the postmaster when I
attempt to create the database. Let me know if getting a trace of
anything will help, if you guys already aren't already
Just wanted to let you know that if we would be interested in adding
that patch to our main cvs the guy who wrote it would be more than
willing to change his license to BSD.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL
Jan Wieck [EMAIL PROTECTED] writes:
I checked the background writer for this and I can not reproduce the
behaviour. If the bgwriter had zero blocks to write it does PG_USLEEP
for 10 seconds, which on Unix is done by select() and that is correctly
interrupted when the postmaster sends it the
On 6 Feb, Tom Lane wrote:
[EMAIL PROTECTED] writes:
Sorry it's taking so long. I tried to take a export from CVS today and
the database appears not to be able to connect to the postmaster when I
attempt to create the database. Let me know if getting a trace of
anything will help, if you
[EMAIL PROTECTED] writes:
creating template1 database in /opt/pgdb/dbt2/base/1 ... ERROR: relnatts disagrees
with indnatts for index 16601
Wow, that's a bizarre one. Are you sure you did a clean rebuild?
I usually like to do make distclean before or after cvs update;
it tends to save me a
I'm using substring. Since I'm a coder more than a database guy, I
expected this:
select substring('abcdefgh',0,4);
would give me
abcd
but it gives me a left aligned 'abc'
select substring('abcdefgh',1,4);
works fine.
select substring('abcdefgh',-4,4);
gives me nothing. Shouldn't a
On 6 Feb, Tom Lane wrote:
[EMAIL PROTECTED] writes:
creating template1 database in /opt/pgdb/dbt2/base/1 ... ERROR: relnatts disagrees
with indnatts for index 16601
Wow, that's a bizarre one. Are you sure you did a clean rebuild?
I usually like to do make distclean before or after cvs
On Thu, 2004-02-05 at 16:51, Josh Berkus wrote:
Tom,
Yes we do: there's a lock.
Sorry, bad test. Forget I said anything.
Personally, I would like to have the 2nd vacuum error out instead of blocking.
However, I'll bet that a lot of people won't agree with me.
Don't know if I
On Fri, 6 Feb 2004, Joe Conway wrote:
scott.marlowe wrote:
gives me nothing. Shouldn't a negative offset, or even 0 offset result in
an error or something here? Or is there a special meaning to a negative
offset I'm not getting?
In varlena.c there is this comment:
*
Tracing the bgwriter process on my machine makes it real
obvious that in
fact the select delay is allowed to finish out when SIGTERM
is received.
In fact worse than that: it's restarted from the beginning. If 5
seconds have already elapsed, another 10 still elapse before
the select
exits.
Tom Lane wrote:
Kevin Brown [EMAIL PROTECTED] writes:
Well, running out of space in the list isn't that much of a problem. If
the backends run out of list space (and the max size of the list could
be a configurable thing, either as a percentage of shared memory or as
an absolute size),
Robert Treat wrote:
On Thu, 2004-02-05 at 16:51, Josh Berkus wrote:
Tom,
Yes we do: there's a lock.
Sorry, bad test. Forget I said anything.
Personally, I would like to have the 2nd vacuum error out instead of blocking.
However, I'll bet that a lot of people won't agree with
What about a situation where someone would have lazy vacuums cron'd and
it takes longer to complete the vacuum than the interval between
vacuums. You could wind up with an ever increasing queue of vacuums.
Erroring out with a vacuum already in progress might be useful.
I have seen this
scott.marlowe [EMAIL PROTECTED] writes:
thanks. I just got done looking up the SQL explanation, and I think my
head exploded. Thanks for the heads up.
The formal definition seems unnecessarily complicated :-(, but the spec
authors' intent is reasonably clear from this paragraph in the
24 matches
Mail list logo
