(cross-posting to HACKERS)
Reuven M. Lerner wrote:
I'm creating a new OpenACS package that uses PostgreSQL, and in doing
so have encountered what seems to be a problem in PostgreSQL.
[...snip...]
> CREATE OR REPLACE FUNCTION add_news__test
> (integer,varchar,timestamptz,varchar,varchar,varchar,
>
Dann Corbit wrote:
-Original Message-
From: Jan Wieck [mailto:[EMAIL PROTECTED]
Sent: Monday, June 23, 2003 10:30 PM
To: Dann Corbit
Cc: scott.marlowe; Bruce Momjian; Tom Lane; Jason Earl;
PostgreSQL-development
Subject: Re: [HACKERS] Two weeks to feature freeze
[snip]
I personally think
> -Original Message-
> From: Josh Berkus [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 23, 2003 10:50 PM
> To: Dann Corbit; Jan Wieck
> Cc: scott.marlowe; Bruce Momjian; Tom Lane; Jason Earl;
> PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to feature freeze
>
>
> Dann,
>
>
Dann,
> Astute members of the list have noticed that I have not volunteered to
> perform the work. I may or may not produce some efforts towards testing
> PostgreSQL. Whether I decide to help or not is irrelevant towards the
> concept of what needs to be done.
It is not irrelevant. This is an
> -Original Message-
> From: Jan Wieck [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 23, 2003 10:30 PM
> To: Dann Corbit
> Cc: scott.marlowe; Bruce Momjian; Tom Lane; Jason Earl;
> PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to feature freeze
[snip]
> I personally think you
Dann Corbit wrote:
-Original Message-
From: Jan Wieck [mailto:[EMAIL PROTECTED]
Sent: Monday, June 23, 2003 10:10 PM
To: scott.marlowe
Cc: Dann Corbit; Bruce Momjian; Tom Lane; Jason Earl;
PostgreSQL-development
Subject: Re: [HACKERS] Two weeks to feature freeze
scott.marlowe wrote:
> On
Here is a list of a small sample of the citations available from the ACM
on software testing:
http://portal.acm.org/citation.cfm?id=581358&coll=portal&dl=ACM&CFID=657
0092&CFTOKEN=81653602
http://portal.acm.org/citation.cfm?id=376180&coll=portal&dl=ACM&CFID=657
0092&CFTOKEN=81653602
http://portal.
> -Original Message-
> From: Jan Wieck [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 23, 2003 10:10 PM
> To: scott.marlowe
> Cc: Dann Corbit; Bruce Momjian; Tom Lane; Jason Earl;
> PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to feature freeze
>
>
> scott.marlowe wrote:
>
we found the problem:
We used IMMUTABLE modifier in our CREATE FUNCTION definition,
though it's correct for our function to return same value if input the
same *data*,
but our data are passed by reference, not by value, so, some times we can't
retrive out data. Remove IMMUTABLE fixed the problem.
scott.marlowe wrote:
On Mon, 23 Jun 2003, Dann Corbit wrote:
> [Dann Corbit wrote a lot]
> [...]
It may be reassuring to think your product is very well tested before it
goes out the door, but it's a false security, proven over and over by
commercial products that simply don't work in the field b
Bruce Momjian wrote:
Well, we have a patch, so we need someone to babysit it until it is
applied, or put it somewhere and reference it via TODO.
OK -- either way is fine by me.
Joe
---(end of broadcast)---
TIP 6: Have you searched our list archive
Well, we have a patch, so we need someone to babysit it until it is
applied, or put it somewhere and reference it via TODO.
---
Joe Conway wrote:
> Bruce Momjian wrote:
> > OK, can you take ownership of it?
> >
>
> You mea
Bruce Momjian wrote:
OK, can you take ownership of it?
You mean a TODO entry? Sure, as long as Hans is OK with it.
Joe
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to
OK, can you take ownership of it?
---
Joe Conway wrote:
> Bruce Momjian wrote:
> > This seems like a natural addition to our existing dblink in /contrib.
> >
>
> Yeah. But we'd need to detect whether or not the Oracle clie
Bruce Momjian wrote:
This seems like a natural addition to our existing dblink in /contrib.
Yeah. But we'd need to detect whether or not the Oracle client libs are
available. I'm not sure how to do that with the contrib build system.
And we'd need a fair amount of integration/reorganizing the ex
Someone's asking this in the PHPBuilder forums:
http://www.phpbuilder.com/board/showthread.php?s=e35a83518b040c2b4db0c7ef3867ab40&threadid=10244626
---
Hi all
Is there a way to disconnect users from a D.B in postgresql rather than
kill -9 the pid user?
thanks in advance
---
Doesn't seem to me
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Should we add an Assert() to make it clear the current code is OK?
A comment maybe, but not an assert.
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscribe c
Looks good to me --- we will include it in 7.4.
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
--
Dann Corbit wrote:
-Original Message-
From: Jan Wieck [mailto:[EMAIL PROTECTED]
What do you think is the way to become an insider?
Join the CVS tree and make a large and valuable contribution to the
project.
Go ahead, let's see it.
I have contributed a lot of crap over the years. After s
Add to TODO:
* Have SELECT '13 minutes'::interval display zero seconds
---
Larry Rosenman wrote:
> Why does the interval type not print seconds when they are zero?
>
> This leads to inconsistent reading of the inf
Added to TODO:
Allow the regression tests to start postmaster with -i so the tests
can be run on systems that don't support unix-domain sockets
---
Tom Lane wrote:
> Kurt Roeckx <[EMAIL PROTECTED]> writes:
> > The regre
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Kurt Roeckx wrote:
> On Fri, Jun 20, 2003
Should we add an Assert() to make it clear the current code is OK?
---
Tom Lane wrote:
> "J.R. Nield" <[EMAIL PROTECTED]> writes:
> > The attached patches against 7.3 and 7.4 fix a subtraction carry bug in
> > xlog.c.
>
> T
Thank's Robert,
that was probably what Bruce needs to call me every other hour now ...
Jan
Robert Treat wrote:
On Sat, 2003-06-21 at 22:55, Bruce Momjian wrote:
Andrew Dunstan wrote:
>
> Maybe a better strategy would be to get a release out soon but not wait 6
> months for another release which
On Tue, 24 Jun 2003, Marc G. Fournier wrote:
>
> The PostgreSQL Core would like to publicly welcome welcome Josh Berkus as
> our newest member.
>
> Josh is being included especially as a "liason" between the
> source-programmer and non-source-programmer contributors to PostgreSQL, in
> an effort t
The PostgreSQL Core would like to publicly welcome welcome Josh Berkus as
our newest member.
Josh is being included especially as a "liason" between the
source-programmer and non-source-programmer contributors to PostgreSQL, in
an effort to expand PostgreSQL volunteer documentation, advocacy, and
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Michael A Nachbaur wrote:
> Attached is a
Added to TODO:
* Rename /scripts directory because they are all C programs now
---
Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > How about just pulling them up a directory into src/bin?
>
> Nah, I don't lik
Add to TODO:
o Allow ALTER TABLE to modify column lengths and change to binary
compatible types
---
Tom Lane wrote:
> "Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> >> There might be other cases o
OK, added to TODO:
Modify pg_get_triggerdef() to take a boolean to pretty-print,
and use that as part of pg_dump along with psql
Andreas, can you work on this? I like the idea of removing extra
parens, and merging it into the existing code rather than into contrib
makes sense.
Josh Berkus wrote:
Anyway, I would vote for a first implemenation for 2PC which addressed the
commit-then-crash issue in some expedient-but-not-reliable way, and putting
2PC in /contrib with a "not for production use" warning. Some people will
use it in production anyway, and hopefully one or m
> Is it me or is there a problem with ftp mirrors?
> The latest shapshots I have here are from June 2; seems rather old..
Also, what happened to www.au.postgresql.org???
Chris
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
OK, patch applied to typedef sa_family_t for cygwin. If other platforms
need it, I will have to do something more generic.
Thanks for the testing. Block removed, though I did have that ISP
marked as cronic, so there must have been a bunch of spam from there,
not just a few.
---
deststar wrote:
> I still seem to get a compile problem (included below).
> Will double check tomorrow when not so tired (02:15 here).
> Cheers,
> - Stuart
> P.S. My server seems to be blacklisted as a spam server by you. Please
> could you white list me.
>
> gcc -O2 -g -Wall -Wmissing-prototypes
On Mon, 23 Jun 2003, Dann Corbit wrote:
> The resistance to testing is typical of programmers. The PostgreSQL
> group is a group of programmers. I don't think I can change anyone's
> mind, since the most significant people on the list don't think it is
> worth the bother.
>
> Therefore, I am goi
On Mon, 23 Jun 2003, Robert Treat wrote:
> > The target-date-based approach we've taken in the last couple of
> > releases seems much more productive.
> >
>
> productive on a small scale; for sure. productive for large scale
> features... well, that's why it's being discussed.
'K, but if we exte
Yes, it does some of that, but I don't think it is safe to do a cvs
update in an automated fashion, as least on my machine.
---
The Hermit Hacker wrote:
>
> On Mon, 23 Jun 2003, Peter Eisentraut wrote:
>
> > Bruce Momjian
On Mon, 23 Jun 2003, Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > Well, it is a nice test template for people who aren't shell script
> > experts, and I have been in the habit of pushing stuff I use into /tools
> > so it is available for others.
>
> I know and I'm not happy about it. Th
I still seem to get a compile problem (included below).
Will double check tomorrow when not so tired (02:15 here).
Cheers,
- Stuart
P.S. My server seems to be blacklisted as a spam server by you. Please
could you white list me.
gcc -O2 -g -Wall -Wmissing-prototypes -Wmissing-declarations
-I../..
Hi,
I have some SQL function, just regular function selects data by using 4
joins nothing fancy,
but one thing pretty noticeable,
I have to display 3 different columns with same date formatted
differently,
here are 3 different snippets:
1. SELECT t.x,t.y,TO_CHAR(t.dt, 'DD/MM/')
FROM
You might still have a problem with compiling getaddrinfo.c. Please let
me know and I can correct it.
---
deststar wrote:
> On cygwin sa_family_t was undeclared, adding the following line:
> typedef unsigned short sa_family
OK, I just applied a patch which should fix cygwin too. Please give it
a try. Thanks.
---
deststar wrote:
> Yes there's:
> struct sockaddr {
>unsigned short sa_family; /* address family, AF_xxx */
>c
I have applied a patch to CVS to fix the problem. It is all your patch,
except for the part you got from me, which was wrong. :-(
It took me a while to realize the subtlety of your patch. First, it
removes the use of sa_family_t _except_ for cases that don't have
SOCKADDR_STORAGE, where it is
Yes there's:
struct sockaddr {
unsigned shortsa_family; /* address family, AF_xxx */
char sa_data[14];/* 14 bytes of protocol address */
};
in socket.h
struct sockaddr {
u_short sa_family;
charsa_data[14];
};
in winsock.h & winsock2.h
deststar, is there any sa_family or ss_family in the cygwin include
directory, perhap with double leading underscores?
---
deststar wrote:
> Jason Tishler wrote:
> > On Sun, Jun 15, 2003 at 04:54:21PM +0100, deststar wrote:
Sorry about that, I had long ago fixed the build, but failed to add it to
cron ... new build created and cron entry added ... :(
On Mon, 23 Jun 2003, Tom Lane wrote:
> [EMAIL PROTECTED] writes:
> > Is it me or is there a problem with ftp mirrors?
> > The latest shapshots I have here are from Ju
> I don't think it could have been said any better. There are a host of
> improvements on the standard 2PC protocol, including 3PC, multi-cast
> 2PC, and other variants both synchronous and asynchronous. But if
> PostgreSQL is going to work with XA, then it doesn't get to choose the
> TM or the pro
I second the agreement ... a 'reference implementation', of sorts, at
least gives someone to build on then starting right from scratch ...
On Mon, 23 Jun 2003, Bruce Momjian wrote:
>
> Agreed.
>
> ---
>
> Josh Berkus wrote
Rod Taylor wrote:
-- Start of PGP signed section.
> > Perhaps the people on this list who are pushing 2PC could do the ground work?
>
>
> - 2PC is better than a standard transaction when dealing with multiple
> servers as it can recover in some circumstances (but not all).
>
> - 2PC (XA suppor
I've run into what seems like an old bug in the character set mapping
for japanese encoding while trying to extract data from my database
using the Java JDBC driver. The problem has to do with the japanese
full-width wave dash.
This problem was brought up by Tom O'Dowd way back in February but
Rod Taylor wrote:
>>Perhaps the people on this list who are pushing 2PC could do the ground work?
>
> - 2PC is better than a standard transaction when dealing with multiple
> servers as it can recover in some circumstances (but not all).
>
> - 2PC (XA support as described by the X/Open group)
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> The behavior that I think would be most useful would be to automatically
> >> transpose CREATE FUNCTION ... LANGUAGE "plpython" into CREATE FUNCTION
> >> ... LANGUAGE "plpythonu". Which we could do with an ugly ha
> Perhaps the people on this list who are pushing 2PC could do the ground work?
- 2PC is better than a standard transaction when dealing with multiple
servers as it can recover in some circumstances (but not all).
- 2PC (XA support as described by the X/Open group) is the only
implementation o
On Monday 23 June 2003 15:42, Dann Corbit wrote:
> Let me rephrase it:
> "Only a cohesive, organized testing effort can result in a product that
> is proven reliable."
One can never 100% prove reliability without time in the field with real-world
data, testing or no testing. I would dare say th
Tom,
"Putting in "dozens of hours" is not the issue here --- the problem is
that there isn't any solution in sight, and I'm not eager to go down a
path that has an obvious dead end."
Well, I doubt we're breaking any new ground with this discussion. If I really
cared about this feature, I would
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> The behavior that I think would be most useful would be to automatically
>> transpose CREATE FUNCTION ... LANGUAGE "plpython" into CREATE FUNCTION
>> ... LANGUAGE "plpythonu". Which we could do with an ugly hack in CREATE
>> FUNCTION (
Tom Lane wrote:
> elein <[EMAIL PROTECTED]> writes:
> > For 7.4 (which I expect is the patch's target) it might be
> > best to make both names point to the same thing with a
> > clear release note that says that they are the same thing
> > and that plpython[u] is now untrusted.
>
> I don't know a
elein <[EMAIL PROTECTED]> writes:
> For 7.4 (which I expect is the patch's target) it might be
> best to make both names point to the same thing with a
> clear release note that says that they are the same thing
> and that plpython[u] is now untrusted.
I don't know any way to actually do that, th
> -Original Message-
> From: Nigel J. Andrews [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 23, 2003 1:30 PM
> To: Dann Corbit
> Cc: scott.marlowe; Bruce Momjian; Tom Lane; Jason Earl;
> PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to feature freeze
[snip]
> So you've never
On Mon, 23 Jun 2003, Dann Corbit wrote:
> > -Original Message-
> > From: scott.marlowe [mailto:[EMAIL PROTECTED]
> > Sent: Monday, June 23, 2003 12:25 PM
> > To: Dann Corbit
> > Cc: Bruce Momjian; Tom Lane; Jason Earl; PostgreSQL-development
> > Subject: Re: [HACKERS] Two weeks to feature
On Mon, 23 Jun 2003, Dann Corbit wrote:
> > -Original Message-
> > From: scott.marlowe [mailto:[EMAIL PROTECTED]
> > Sent: Monday, June 23, 2003 12:25 PM
> > To: Dann Corbit
> > Cc: Bruce Momjian; Tom Lane; Jason Earl; PostgreSQL-development
> > Subject: Re: [HACKERS] Two weeks to feature
Dann Corbit wrote:
> Let me rephrase it:
> "Only a cohesive, organized testing effort can result in a product that
> is proven reliable."
>
> Without such an effort, it is only an educated guess as to whether the
> product is reliable or not. The data is the most valuable software
> component in
scott.marlowe wrote:
> Peter is coming off awfully paternalistic here. I'd rather have a few
> extra scripts to look through to find what I need when I'm trying to
> figure out something than to have a tool that only the hackers know exists
> and I can only get by asking nicely to see the prett
> -Original Message-
> From: scott.marlowe [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 23, 2003 12:25 PM
> To: Dann Corbit
> Cc: Bruce Momjian; Tom Lane; Jason Earl; PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to feature freeze
>
>
> On Mon, 23 Jun 2003, Dann Corbit wrot
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > I put stuff in /tools so if something happens to me, you guys can keep
> > going.
>
> Yes, we keep going with make clean; make check, like everyone else. Why
> don't you consider using that?
Actually, I used to manually do all those tests to
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > I put stuff in /tools so if something happens to me, you guys can keep
> > going.
>
> Yes, we keep going with make clean; make check, like everyone else. Why
> don't you consider using that?
The script is automated to run at night, it captur
On Mon, 23 Jun 2003, Bruce Momjian wrote:
> Peter Eisentraut wrote:
> > Bruce Momjian writes:
> >
> > > Well, it is a nice test template for people who aren't shell script
> > > experts, and I have been in the habit of pushing stuff I use into /tools
> > > so it is available for others.
> >
> >
On Mon, 23 Jun 2003, Dann Corbit wrote:
> Vendor A: "We think our tool is pretty solid and our end users hardly
> ever turn up any bugs."
>
> Vendor B:" We think our tool is pretty solid and our 8500 tests
> currently show only 3 defects with the released version, and these are
> low impact issue
Bruce Momjian writes:
> I put stuff in /tools so if something happens to me, you guys can keep
> going.
Yes, we keep going with make clean; make check, like everyone else. Why
don't you consider using that?
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)
Dann Corbit wrote:
> PostgreSQL is a fairly mature product, having been in existence in one
> form or another for many years now.
>
> I expect that most of the bugs that surface will be in areas of new
> functionality.
>
> Great Bridge had the right idea though. Let's suppose that they ran
> 10,
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > Well, it is a nice test template for people who aren't shell script
> > experts, and I have been in the habit of pushing stuff I use into /tools
> > so it is available for others.
>
> I know and I'm not happy about it. The PostgreSQL source t
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]
> Sent: Saturday, June 21, 2003 8:50 PM
> To: Dann Corbit
> Cc: Tom Lane; Jason Earl; PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to feature freeze
>
>
> Dann Corbit wrote:
> > That is the worst possible t
"Dann Corbit" <[EMAIL PROTECTED]> writes:
>> What do you think is the way to become an insider?
> Join the CVS tree and make a large and valuable contribution to the
> project.
For instance, developing an industrial-strength test suite? If you've
got an itch there, scratch it.
Bruce Momjian writes:
> Well, it is a nice test template for people who aren't shell script
> experts, and I have been in the habit of pushing stuff I use into /tools
> so it is available for others.
I know and I'm not happy about it. The PostgreSQL source tree isn't a
repository of everyone's f
> -Original Message-
> From: Jan Wieck [mailto:[EMAIL PROTECTED]
> Sent: Sunday, June 22, 2003 5:45 AM
> To: Dann Corbit
> Cc: Tom Lane; Jason Earl; PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to feature freeze
>
>
> Dann Corbit wrote:
> >> -Original Message-
> >> F
> -Original Message-
> From: The Hermit Hacker [mailto:[EMAIL PROTECTED]
> Sent: Sunday, June 22, 2003 12:30 PM
> To: Jan Wieck
> Cc: The Hermit Hacker; Dann Corbit; Tom Lane; Jason Earl;
> PostgreSQL-development
> Subject: Re: [HACKERS] Two weeks to feature freeze
>
>
> On Sun, 22 Jun
Randall Lucas <[EMAIL PROTECTED]> writes:
> The LIKE operator takes a pattern, and since your pattern did not
> specify a wildcard at the end, it didn't exactly match the padded
> string.
> This behavior does seem kind of confusing;
Yeah. As of CVS tip, the system is actually going out of its
This seems like a natural addition to our existing dblink in /contrib.
---
Hans-Jürgen Schönig wrote:
> Hi there ...
>
> I have spent some time working on an Oracle version of dblink. It works
> quite nicely for me and I h
Josh Berkus <[EMAIL PROTECTED]> writes:
>> No. I want to know what the subordinate does when it's promised to
>> commit and the co-ordinator never responds. AFAICS the subordinate
>> is screwed --- it can't commit, and it can't abort, and it can't expect
>> to make progress indefinitely on other
Scott MArlowe wrote:
> On Sat, 21 Jun 2003, Bruce Momjian wrote:
>
>> The big puzzle is how do you get people (including myself) motivated
>> to work on a feature that takes a _huge_ amount of work to see any
>> payoff? I would like to know. Anyone?
>
> Pizza? :-)
Unfortunately it's off my die
On Mon, 23 Jun 2003, Bruce Momjian wrote:
> Peter Eisentraut wrote:
> > The Hermit Hacker writes:
> >
> > > Ya, the script looked like it did a bit more then just a 'make clean; make
> > > check' ... doesn't it?
> >
> > No.
>
> Well, it is a nice test template for people who aren't shell script
Robert Treat <[EMAIL PROTECTED]> writes:
> Here's a sure to be wildly unpopular suggestion:
> Make the deciding factor for the next release support of "foo" (foo can
> be win32, pitr, replication, 2PC, whatever...).
We've done that before (see WAL in 7.1), with unhappy results. The
fundamental p
[EMAIL PROTECTED] writes:
> Is it me or is there a problem with ftp mirrors?
> The latest shapshots I have here are from June 2; seems rather old..
It's not the mirrors' fault --- the nightly snapshots aren't getting
updated on the master site either. I think this is still on Marc's
"to fix" list
On Monday 23 June 2003 10:43 am, Tom Lane wrote:
> Robert Treat <[EMAIL PROTECTED]> writes:
> > Here's a sure to be wildly unpopular suggestion:
> >
> > Make the deciding factor for the next release support of "foo" (foo can
> > be win32, pitr, replication, 2PC, whatever...).
>
> We've done that be
On Sat, 2003-06-21 at 22:55, Bruce Momjian wrote:
> Andrew Dunstan wrote:
> >
> > Maybe a better strategy would be to get a release out soon but not wait 6
> > months for another release which would contain the Win32 port and the PITR
> > stuff (assuming those aren't done in time for this release)
Peter Eisentraut wrote:
> The Hermit Hacker writes:
>
> > Ya, the script looked like it did a bit more then just a 'make clean; make
> > check' ... doesn't it?
>
> No.
Well, it is a nice test template for people who aren't shell script
experts, and I have been in the habit of pushing stuff I use
Agreed.
---
Josh Berkus wrote:
> Tom,
>
> > No. I want to know what the subordinate does when it's promised to
> > commit and the co-ordinator never responds. AFAICS the subordinate
> > is screwed --- it can't commit, and
The Hermit Hacker writes:
> Ya, the script looked like it did a bit more then just a 'make clean; make
> check' ... doesn't it?
No.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
just have a quick question. What i need to do is to create a shared memory
structure (which i can do) and maintain in it a linked list which should
be in shared memory too. I found the shmemqueue in postgres, but am having
some problems using it. I just need to have the linked list store
relation
Tom,
> No. I want to know what the subordinate does when it's promised to
> commit and the co-ordinator never responds. AFAICS the subordinate
> is screwed --- it can't commit, and it can't abort, and it can't expect
> to make progress indefinitely on other work while it's holding locks
> for th
Hi Mark
Is it me or is there a problem with ftp mirrors?
The latest shapshots I have here are from June 2; seems rather old..
Regards
--
Olivier PRENANT Tel:+33-5-61-50-97-00 (Work)
Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax)
31190 AUTERIVE
On Sat, 21 Jun 2003, Bruce Momjian wrote:
> Andrew Dunstan wrote:
> >
> > Maybe a better strategy would be to get a release out soon but not wait 6
> > months for another release which would contain the Win32 port and the PITR
> > stuff (assuming those aren't done in time for this release).
>
>
On Sat, 21 Jun 2003, Christopher Kings-Lynne wrote:
> Crash-me has nothing to do with testing, it jsut checks to see what
> features a db supports:
An interesting point is that until recently, crashme said that the
postgresql backend crashed on very large queries. The actual problem was
that p
On Mon, 23 Jun 2003, Srikanth M wrote:
> Hi!
> Can anyone give me the informatoin reagarding the last date of
> submission of the code to be added in next version of pgsql.
June 30th ...
---(end of broadcast)---
TIP 3: if posting/reading t
Hi!
Can anyone give me the informatoin reagarding the last date of
submission of the code to be added in next version of pgsql.
bye
Srikanth
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
On Saturday 21 Jun 2003 11:04 pm, _ wrote:
> Hi
>
> Thanks for the reply especially since I have resigned
> myself not to use schema anymore and
> unsubscribed from the list. (I subscribed just to post)
I've CCd this back to the hackers list, since others may have something to
contribute here.
>
> > > > Copy to table (DB has UTF-8 encoding) from file:
> > > > for PGCLIENTENCODING=BIG5:
> > > > WARNING: copy: line 1, LocalToUtf: could not convert (0xf9d6) BIG5 to UTF-8.
> > > > Ignored
> > > > WARNING: copy: line 2, LocalToUtf: could not convert (0xf9d7) BIG5 to UTF-8.
> > > > Ignored
>
> > > Copy to table (DB has UTF-8 encoding) from file:
> > > for PGCLIENTENCODING=BIG5:
> > > WARNING: copy: line 1, LocalToUtf: could not convert (0xf9d6) BIG5 to UTF-8.
> > > Ignored
> > > WARNING: copy: line 2, LocalToUtf: could not convert (0xf9d7) BIG5 to UTF-8.
> > > Ignored
> > > WARNING
98 matches
Mail list logo
