would really look
like, but given the feedback provided here, it's worth investigating.
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
like the end of the world. Clearly the user here is writing postgresql
specific code to use hstore operators, so there's not a portability loss
here.
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
some other connection
types because it uses InputStream.available that not all
implementations support.
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 2 November 2011 16:35, Brar Piening b...@gmx.de wrote:
See http://de.wikipedia.org/wiki/Unendlichkeit#Analysis
(Sorry for linking the german wikipedia - the english text is ways less
verbose on this.)
Google Translate has come a very long way.
I can read that whole section easily with my
if this file was marked executable in git.
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Fri, 19 Aug 2011, Kris Jurka wrote:
For me this fails with:
Bareword Tie::File not allowed while strict subs in use at
/home/jurka/pg/server/postgresql/src/tools/copyright.pl line 28.
This fixes things for me. The copyright matching wasn't working for me
either without escaping
gets it back to the file.
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
should try to avoid adding extra dependencies wherever possible.
I can easily change this to rewrite files that contain copyright changes
--- should I?
No. We don't need a super portable copyright year changing script.
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql-hackers
On Tue, 19 Apr 2011, Tom Lane wrote:
Kris Jurka bo...@ejurka.com writes:
On Mon, 18 Apr 2011, Mike Fowler wrote:
As there seems to be a consensus forming for fixing the JDBC driver, I've
taken the liberty do so at the risk of being shot down. The patch is fairly
straightforward, just
. Those Unicode
mentions are from the interface Javadoc, so I left them alone.
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 3 March 2011 06:33, Andy Colson a...@squeakycode.net wrote:
On 1/23/2011 5:11 AM, Michael Meskes wrote:
As I already said when the script was introduced, I would love to have a
real
perl solution, but I'm not a perl programmer by any means.
Michael
I thought Kris was going to work
On 24 January 2011 03:06, Andrew Dunstan and...@dunslane.net wrote:
It's doing the right thing. But it's really spaghetti code, generated by
a2p. Matt was just (rightly) offended by the $[ setting, IIRC.
The point is that it's close to being totally unmaintainable.
But if you think you can
On 23 January 2011 14:28, Kris Shannon k...@shannon.id.au wrote:
On 23 January 2011 13:14, Andrew Dunstan and...@dunslane.net wrote:
But there are quite a few perlheads around. ISTR Matt Trout was muttering
about these scripts on IRC recently.
A quick cleanup of the check_rules.pl...
It's
On 23 January 2011 13:14, Andrew Dunstan and...@dunslane.net wrote:
But there are quite a few perlheads around. ISTR Matt Trout was muttering
about these scripts on IRC recently.
A quick cleanup of the check_rules.pl...
It's a starting point at least.
ecpg_prepoc_check_rules_cleanup.patch
it
made sense to put it in the commitfest, but as far as I understand it,
this one is pure Java code. There is a backlog of JDBC issues to deal
with, but I think it needs its own commitfest instead of trying to tack on
to the main project's.
Kris Jurka
--
Sent via pgsql-hackers mailing list
On Sat, 7 Aug 2010, Kris Jurka wrote:
On Fri, 6 Aug 2010, James William Pye wrote:
I think there's a snag in the patch:
postgres=# COPY data FROM '/Users/jwp/DATA.bcopy' WITH BINARY;
ERROR: row field count is -1, expected 1
CONTEXT: COPY data, line 4
Probably a quick/small fix away, I
On Fri, 6 Aug 2010, James William Pye wrote:
On Aug 6, 2010, at 4:31 PM, Kris Jurka wrote:
binary-copy-end-v2.patch
I think there's a snag in the patch:
postgres=# COPY data FROM '/Users/jwp/DATA.bcopy' WITH BINARY;
ERROR: row field count is -1, expected 1
CONTEXT: COPY data, line 4
if there is any more data does ensure
that if there isn't any more data in the current buffer, that we wait for
the client to provide CopyDone/Fail.
Kris Jurka*** a/src/backend/commands/copy.c
--- b/src/backend/commands/copy.c
***
*** 2058,2069 CopyFrom(CopyState cstate
to the server, so
without parsing all of that we don't know whether they've issued
CopyData(EOF) or not.
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Sat, 24 Jul 2010, James William Pye wrote:
On Jul 23, 2010, at 7:11 AM, Tom Lane wrote:
I can't help thinking that the JDBC driver must be being overly cute
if this breaks it ...
I was wondering the same thing when I first saw Kris' message. However,
iff I understand what JDBC
On Thu, 22 Jul 2010, Robert Haas wrote:
On Thu, Jul 22, 2010 at 5:34 PM, Kris Jurka bo...@ejurka.com wrote:
Attached is a patch to make the server continue to consume protocol data
until instructed to stop by the client in the same way as copying text data
to the server currently works
On 7/23/2010 6:40 AM, Tom Lane wrote:
Kris Jurkabo...@ejurka.com writes:
Attached is a patch to make the server continue to consume protocol data
until instructed to stop by the client in the same way as copying text
data to the server currently works.
I believe this is a misunderstanding
On Fri, 23 Jul 2010, Tom Lane wrote:
Kris Jurka bo...@ejurka.com writes:
On 7/23/2010 6:40 AM, Tom Lane wrote:
I believe this is a misunderstanding of the protocol spec. The spec is
(intended to say that) we'll continue to accept data after reporting an
error, not that we will silently
way as copying text
data to the server currently works.
http://www.postgresql.org/docs/8.4/static/protocol-flow.html#PROTOCOL-COPY
http://www.postgresql.org/docs/8.4/static/sql-copy.html
Kris Jurka*** a/src/backend/commands/copy.c
--- b/src/backend/commands/copy.c
***
*** 2058,2069
.
The JDBC driver uses pg_get_expr to decode both pg_attrdef.adbin and
pg_index.indpred.
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
the desired
timeout.
http://java.sun.com/javase/6/docs/api/java/net/Socket.html#setKeepAlive%28boolean%29
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
is not valid. By default the driver switches to using
a named statement after the same PreparedStatement object is executed five
times.
http://jdbc.postgresql.org/documentation/84/connect.html#connection-parameters
http://jdbc.postgresql.org/documentation/84/server-prepare.html
Kris Jurka
--
Sent
.
Already this is tough because of the asynchronous nature of the cancel
protocol and the inability to say exactly what should be cancelled.
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
gets error message from saying the transaction was cancelled.
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
was cancelled.
Are you saying that the client should send rollback and that it should
generate no message?
No, I'm saying if for some business logic reason the client decided it
needed to rollback as it hadn't seen the error message yet.
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql
at the ERROR.
+1
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
this
logging on your JDBC client would show more clearly what it is trying to
do.
Kris Jurkaimport java.sql.*;
public class Crash {
public static void main(String args[]) throws Exception {
Class.forName(org.postgresql.Driver);
Connection conn
the driver's protocol handling and it thinks that the error
message is for the next statement issued.
Attached is a test case.
Kris Jurka
import java.sql.*;
public class Cancel {
public static void main(String args[]) throws Exception {
Class.forName
is that they weren't
able to pull newer updates as well which seems like a net loss.
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
of SELECT
''::bytea, or is there some padding happening somewhere that makes this
legal?
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
doesn't matter) we can do for
custom_variable_classes?
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
.
http://java.sun.com/javase/6/docs/api/java/sql/Connection.html#setClientInfo(java.lang.String,%20java.lang.String)
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
a firewall
(or ssh tunnel) that did port forwarding. What PG binds to and what a
client connects to may not be the same thing.
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Tom Lane wrote:
I see buildfarm member canary (NetBSD 1.6) was recently resurrected,
but is failing to build HEAD, because msgfmt fails like this:
po/es.po:8039: keyword msgid_plural unknown
po/es.po:8036: missing `msgstr' section
po/es.po:8039: parse error
This indicates (1) canary needs a
Tom Lane wrote:
What I'd suggest Kris do is temporarily disable the NLS option on that
build, so we can get at least some useful testing from the machine.
After a proposed configure fix has been installed, re-enable NLS, verify
configure fails as expected, *then* upgrade msgfmt.
I disabled
2009/6/7 Tom Lane t...@sss.pgh.pa.us:
So there are a lot of good reasons to work backwards in patching.
I don't believe that these would be outweighed by some advantage
in the mechanics of applying an unchanging patch to multiple
branches (especially since AFAICT the mechanical advantage would
/message-id/87zlnwnvjg@news-spur.riddles.org.uk
That's a pretty overwhelming argument for leaving it as-is. I think
we should remove this from the list of open items.
Yes, that makes sense to me as the original requester of this open item.
I thought it had been taken off a while ago.
Kris
On Wed, 18 Feb 2009, Kris Jurka wrote:
I have reviewed pljava's handling of misrepresented alignment, length, and by
value parameters [and it doesn't all work.]
I have fixed pljava to now correctly handle all of these being defined
incorrectly. So a trusted language can be used
. The fact that no PL currently does it correctly is not a reason
to prohibit a PL from doing it correctly.
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Thomas Hallgren wrote:
Kris Jurka wrote:
3) By value: pljava does not correctly handle passed by value types
correctly, allowing access to random memory.
This is simply not true. There's no way a Java developer can access
random memory through PL/Java.
No, the point is that the Java
.
Breaks the build with --enable-thread-safety and --with-openssl because
of this typo.
Kris Jurka
*** a/src/interfaces/libpq/fe-secure.c
--- b/src/interfaces/libpq/fe-secure.c
***
*** 918,925 destroy_ssl_system(void)
* This means we leak a little memory on repeated load
On Wed, 26 Nov 2008, Dave Page wrote:
It's the same IP address - but try port 35 for ssh. Marc changed it
(temporarily) due to a vast number of malicious connection attempts.
Why wasn't this change communicated to anyone, not even gforge-admins?
How temporary is temporary?
Kris Jurka
/msg01510.php
Kris Jurka*** a/src/backend/access/transam/twophase.c
--- b/src/backend/access/transam/twophase.c
***
*** 122,128 typedef struct GlobalTransactionData
typedef struct TwoPhaseStateData
{
/* Head of linked list of free GlobalTransactionData structs
On Tue, 28 Oct 2008, Zdenek Kotala wrote:
Kris Jurka napsal(a):
Here's a patch that changes everything over to the the new API and
implements the old API by calling the new API.
It seems to me OK. I have only one comment. I prefer to pfree allocated
memory for temporary nulls array. I
On Thu, 23 Oct 2008, Kris Jurka wrote:
The problem with trying to deprecate it is that the vast majority of the
backend is still using the old interfaces, so people looking for
inspiration for their external modules will likely end up using the old
interface. Like Alvaro I started
a while ago, got bored,
and forgot about it. If people do want this conversion done while keeping
the old interface around, I can track down that patch, update it and
finish it up for the next CommitFest.
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
On Mon, 13 Oct 2008, Tom Lane wrote:
I notice now that kudu and dragonfly are actually the same machine ...
could this be an OS-specific problem? Kris, has there been any
system-software change on that machine recently?
This is a VM that I haven't touched in some time. It was turned off
printTableInit.
3) When describing a sequence it queries the sequence by name and was not
schema qualifying it which is necessary when describing objects not in the
search path. This is still busted because it does not correctly quote the
identifiers.
Kris JurkaIndex: src/bin/psql/describe.c
java.lang.String.
http://wiki.tada.se/display/pljava/Creating+a+Scalar+UDT+in+Java
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Tue, 17 Jun 2008, Alvaro Herrera wrote:
Maybe, or maybe not. Do these platforms all have Perl?
Of course. They're all buildfarm clients and the buildfarm script is
perl.
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
lonely ;)
The JDBC driver would also like this ability, but a GUC is a pretty ugly
hack. Also, since you still have to go to the SQL level to issue the MOVE
or FETCH BACKWARD, you're still not all the way there to a full protocol
solution.
Kris Jurka
--
Sent via pgsql-hackers mailing list
it up to be
able to use the extended query protocol. So the JDBC driver is actually
doing the reverse of your suggestion. For us it was a decision to ease
the transition from V2 to V3 protocol and not break code that used to
work.
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql
?
Are you having any actual problems or is this all theoretical? I don't
believe you should be having any issues, but if you're having a real
problem, please post a self-contained test case so we can look into it.
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
available of PostGre
8.3.0 having this stack_depth check disabled?
This was fixed in postgresql/pljava shortly after the referenced
discussion. As requested, postgresql 8.1+ allows modification of
stack_base_ptr so pljava can set it as desired.
Kris Jurka
--
Sent via pgsql-hackers mailing list
will. So clearly 4.3 is doing something new here, but that doesn't prove
we're safe on previous versions.
[1] http://www.airs.com/blog/archives/120
Kris Jurka
exec.c:245: warning: assuming signed overflow does not occur when changing X +-
C1 cmp C2 to X cmp C1 +- C2
exec.c:245: warning: assuming
://www.airs.com/blog/archives/120
Kris Jurka
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Fri, 15 Feb 2008, Michael Meskes wrote:
Could anyone please tell me how NetBSD defines dtime_t? We have a
buildfarm failure on canary.
/usr/include/sys/types.h says:
typedef int32_t dtime_t;/* on-disk time_t */
Kris Jurka
---(end of broadcast
] with a null byte?
Kris Jurka
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
On Tue, 5 Feb 2008, Magnus Hagander wrote:
On Tue, Jan 29, 2008 at 03:34:19AM -0500, Kris Jurka wrote:
Is it possible to authenticate using GSSAPI over the V2 protocol? Is
there any documentation on the message formats for V2?
Honestly - don't know :-) Never looked at that part. I mean
/2008-01/threads.php#00144
Kris Jurka
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list
Is it possible to authenticate using GSSAPI over the V2 protocol? Is
there any documentation on the message formats for V2?
Kris Jurka
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org
language have little in common.
I've put up a new pljava build against 8.2.6 for windows here:
http://www.ejurka.com/pgsql/pljava/826/
In this case you need the new pljava.jar as well as the .dll because
it's had some updates since the previous release as well.
Kris Jurka
.
The easiest thing to do would be to drop the default comment. Then only
custom comments would be dumped at all (at least for 8.3+ dbs). It's not
like Standard public schema is particularly enlightening.
Kris Jurka
---(end of broadcast)---
TIP
On Thu, 10 Jan 2008, Jan Ischebeck wrote:
8.3beta3 and 4 have worked perfectly with the provided pljava ddl, just
with 8.3-rc1 it doesn't work anymore.
8.3RC1 changed the function definition for SetUserId, so it pljava needs
some changes and a rebuild. Will fix.
Kris Jurka
On Thu, 10 Jan 2008, Kris Jurka wrote:
On Thu, 10 Jan 2008, Jan Ischebeck wrote:
8.3beta3 and 4 have worked perfectly with the provided pljava ddl, just
with 8.3-rc1 it doesn't work anymore.
8.3RC1 changed the function definition for SetUserId, so pljava needs
some changes and a rebuild
the
jar file in various sqlj tables that the calling user may not be able to
write to, but it wants to create the tables and function specified in the
deployement descriptor with the ownership of the user calling install_jar,
not the person who initially installed pljava.
Kris Jurka
as a contributor to the original feature rather
than calling it out as a separate item?
Kris Jurka
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so
out with a helpful message as this isn't
the first time people have been bitten by that change.
Kris Jurka
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining
releases. Upgrade pg to the top of REL8_2_STABLE or downgrade mingw.
http://archives.postgresql.org/pgsql-committers/2007-11/msg00566.php
Kris Jurka
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
, but it wasn't built shared, so I can't test
plperl. I ran the test case Greg posted to the perl bug tracker and it
doesn't fail, so unless you're concerned that your change will break 5.6,
then it doesn't look like 5.6 needs a fix.
Kris Jurka
---(end of broadcast
problem?
Kris Jurka
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
Magnus Hagander wrote:
Where in the US? We generally list at least the state for ppl int he US
- most often both city+state. (shows up only for people listed as major
developers for the time being, which is why nobody asked for it before)
Denver, CO
Kris Jurka
On Tue, 27 Nov 2007, Josh Berkus wrote:
Kris Jurka, Finland
USA actually.
Kris Jurka
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Magnus Hagander wrote:
Log Message:
---
New versions of mingw have gettimeofday(), so add an autoconf test
for this.
Can we backport this fix? I'm trying to setup a new windows build
environment and this is currently halting my progress for back branches.
Kris Jurka
: a tool to view the differences between two
diffs!
I wouldn't trust that too much. I've played with it quite a bit and there are
quite a few corner cases where it gives the wrong answer (or at least a
different diff than I get when I manually apply them and then take the diff)
--
Kris Shannon
(not
exactly every 4 hours, the intervals vary between 3 and 4 1/2 hours).
I wonder if we could get trout back in the rotation, too?
Both trout and eel are permanently dead due to a drive failure. I can
potentially setup new animals next week, but these are gone.
Kris Jurka
/btree_gist/btree_bit.c?sortby=date;only_with_tag=REL7_4_STABLE
I'm not sure what's going on here, but something has gone bad.
Kris Jurka
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
On Fri, 13 Jul 2007, Zdenek Kotala wrote:
Tom Lane wrote:
Kris Jurka [EMAIL PROTECTED] writes:
So pam_message ** isn't const.
Ah, thanks. I see luna_moth is giving the same warning, so it's still
not const in Solaris 11 either.
Is it worth working around this? It's strictly cosmetic
machines?
struct pam_conv {
int (*conv)(int, struct pam_message **,
struct pam_response **, void *);
void *appdata_ptr; /* Application data ptr */
};
So pam_message ** isn't const.
Kris Jurka
---(end of broadcast
the system
provided printf which is why it was only seen on NetBSD although in could
have been seen on mingw as well.
Kris Jurka
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
. It is possible that members
are configured with --keepall, which keeps the entire directory tree if a
failure occurs. That can fill up a lot of space quickly when you get a
failure.
Kris Jurka
---(end of broadcast)---
TIP 4: Have you searched
On Mon, 4 Jun 2007, Kris Jurka wrote:
On Mon, 4 Jun 2007, Andrew Dunstan wrote:
turnip_moth is also a Solaris 9 box and doesn't seem have the same issue.
Kris, is there anything unusual installed on the box that would make it
behave like this?
Not sure what's going on here. I did
numeric constant in a SQL statement via Pqfsize
SELECT 3::numeric;
Kris Jurka
---(end of broadcast)---
TIP 6: explain analyze is your friend
On Mon, 4 Jun 2007, Andrew Dunstan wrote:
turnip_moth is also a Solaris 9 box and doesn't seem have the same issue.
Kris, is there anything unusual installed on the box that would make it
behave like this?
Not sure what's going on here. I did a manual run of the ecpg tests
client_encoding =
UNICODE the server responds with a ParameterStatus message of
client_encoding = server encoding. So something has gone wrong here.
It's not just a UNICODE/UTF-8 problem as I see the server responding with
LATIN1 with a LATIN1 database.
Kris Jurka
repository dates, but a svn checkout
will use the current time unless you enable a config option for your
local svn client.
Kris Jurka
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http
On Thu, Apr 12, 2007 at 12:57:32PM -0400, Bruce Momjian wrote:
Tom Lane wrote:
Kris Kennaway [EMAIL PROTECTED] writes:
On Wed, Apr 11, 2007 at 01:03:50AM -0400, Tom Lane wrote:
Well, the thing is, we've pretty much had it handed to us that
current-command indicators that aren't up
On Tue, Apr 10, 2007 at 10:41:04PM +1200, Mark Kirkwood wrote:
Kris Kennaway wrote:
If so, then your task is the following:
Make SYSV semaphores less dumb about process wakeups. Currently
whenever the semaphore state changes, all processes sleeping on the
semaphore are woken, even if we
On Tue, Apr 10, 2007 at 10:23:42AM -0400, Tom Lane wrote:
Mark Kirkwood [EMAIL PROTECTED] writes:
Kris Kennaway wrote:
If so, then your task is the following:
Make SYSV semaphores less dumb about process wakeups. Currently
whenever the semaphore state changes, all processes sleeping
On Tue, Apr 10, 2007 at 03:52:00PM -0400, Tom Lane wrote:
Kris Kennaway [EMAIL PROTECTED] writes:
On Tue, Apr 10, 2007 at 02:46:56PM -0400, Tom Lane wrote:
Oh, I'm sure the BSD kernel acts as you describe. But Mark's point is
that Postgres never has more than one process waiting on any
On Tue, Apr 10, 2007 at 08:23:36PM -0400, Tom Lane wrote:
I think the high number of setproctitle() calls are more problematic
to us at the moment, Kris can comment on that.
As of PG 8.2 it is possible to turn those off. I don't think there's a
lot of enthusiasm for turning them off
On Tue, Apr 10, 2007 at 06:26:37PM -0400, Tom Lane wrote:
Kris Kennaway [EMAIL PROTECTED] writes:
On Tue, Apr 10, 2007 at 05:36:17PM -0400, Tom Lane wrote:
Anyway I'd be interested to know what the test case is, and which PG
version you were testing.
I used 8.2 (and some older version
On Wed, Apr 11, 2007 at 12:50:06PM +1200, Mark Kirkwood wrote:
Tom Lane wrote:
I think the high number of setproctitle() calls are more problematic
to us at the moment, Kris can comment on that.
As of PG 8.2 it is possible to turn those off. I don't think there's a
lot of enthusiasm
On Wed, Apr 11, 2007 at 01:03:50AM -0400, Tom Lane wrote:
Kris Kennaway [EMAIL PROTECTED] writes:
I think the high number of setproctitle() calls are more problematic
to us at the moment, Kris can comment on that.
Since we've basically had it handed to us that calling setproctitle
On Tue, Apr 10, 2007 at 02:46:56PM -0400, Tom Lane wrote:
Kris Kennaway [EMAIL PROTECTED] writes:
Make SYSV semaphores less dumb about process wakeups. Currently
whenever the semaphore state changes, all processes sleeping on the
semaphore are woken, even if we only have released enough
1 - 100 of 222 matches
Mail list logo
