Debian packages of 7.3 for i386 architecture are available in Debian's
unstable archive, as those people tracking unstable will already have
noticed. I will get round to producing packages for stable when all the
immediate problems are fixed.
There are various packaging bugs that I am working on;
Lamar Owen wrote:
However, I seriously question the need in the long term for our sites to be as
fractured as they are. Good grief! We've got advocacy.postgresql.org,
techdocs.postgresql.org, odbc.postgresql.org, gborg.postgresql.org,
developer.postgresql.org, jdbc.postgresql.org, etc. Oh, a
Kevin Brown wrote:
> Christopher Kings-Lynne <[EMAIL PROTECTED]> wrote:
> > Hi guys,
> >
> > Just out of interest, if someone was going to pay you to hack on Postgres
> > for 6 months, what would you like to code for 7.4?
>
> Well, on top of the oft-requested replication support and savepoint
> s
I am not going to apply this patch because I think it will mess up the
handling of other locales.
---
Nicolai Tufar wrote:
> Hi,
>
> Yet another problem with Turkish encoding. clean_encoding_name()
> in src/backend/utils/m
I am not sure you are going to be happy with our nested transactions.
Your text is:
> (1) embedded transactions
> - i.e. the "outer" transaction can rollback an "inner" committed
> transaction
> - currently the commit of the inner transaction would commit statements
> of the inner and outer tran
Dan, is this ready to be applied to CVS?
---
Dan Langille wrote:
> I have been looking at contrib/ltree in the PostgreSQL repository. I've
> modified the code to allow / as a node delimiter instead of . which is the
> defau
if I create a table like this "create table test (nuber int4,id_num
int4,primary key(id_num));"
My question is, ¿ I can do this ?
"insert into test (number) values (10);"
"insert into test (number) values (22);"
"insert into test (number) values (3);"
and make a function to insert the correct id_n
I have built and am uploading RPMS for 7.3. Mirror propagation being what it
is, it may take a day or two for these packages to make the rounds.
You may find them at:
ftp://ftp.postgresql.org/pub/binary/v7.3/RPMS
Source RPM in SRPMS, Red Hat 8 RPMS in redhat-8.0. I will be building Red Hat
7.
On Thu, 5 Dec 2002, Philip Warner wrote:
> What are the consequences of the problem?
Speaking from the perspective of a long time postgresql user, who
currently has several very mission critical applications using postgresql
on the back end, at a very large company...
I can say the one conseque
Yes, I get the same failure. with perl 5.005_03. Steven, can you
comment on this?
---
Tatsuo Ishii wrote:
> Hi, I have been playing around with contrib/dbmirror with RC2 and
> faced with following errors:
>
> perl DBMirro
Robert Treat wrote:
> On Wed, 04 Dec 2002 22:54:37 -0500, Philip Warner wrote:
> > At 05:48 PM 4/12/2002 -0800, Christopher Kings-Lynne wrote:
> >>Lack of marketing is one of Postgres's major problems.
> >
> > What are the consequences of the problem?
> >
>
> One consequence that probably hits h
On Wed, 04 Dec 2002 22:54:37 -0500, Philip Warner wrote:
> At 05:48 PM 4/12/2002 -0800, Christopher Kings-Lynne wrote:
>>Lack of marketing is one of Postgres's major problems.
>
> What are the consequences of the problem?
>
One consequence that probably hits home for everyone here is it makes it
Tom Lane wrote:
> Tomas Berndtsson <[EMAIL PROTECTED]> writes:
> > After it tries again, it always gets error from recv() for some reason
> > that I don't know. I also don't understand why errno is set to ENOTTY
> > at this point, that makes no sense at all.
>
> Are you sure it is set? Try settin
[cc: list trimmed]
On Wednesday 04 December 2002 22:52, Philip Warner wrote:
> At 05:48 PM 4/12/2002 -0800, Christopher Kings-Lynne wrote:
> >Lack of marketing is one of Postgres's major problems.
> What are the consequences of the problem?
Actually, lack of easy upgrading is one of PostgreSQL's
At 05:48 PM 4/12/2002 -0800, Christopher Kings-Lynne wrote:
Lack of marketing is one of Postgres's major problems.
What are the consequences of the problem?
Particularly when you compare against similar efforts from MySQL, Oracle,
etc.
You could even include Microsoft here - they do a lot o
> > > It isn't, but those working on -advocacy were asked to help come up with
> a
> > > stronger release *announcement* then we've had in the past ...
> >
> > Consider that a failed experiment. PostgreSQL is driven by the
> > development group and, to some extent, by the existing user base. The
I sent this message to pgsql-performance yesterday, but as of now (about 30
hours later) I haven't yet received a response. So I figured I'd see what
you guys think. Please help if you can. Thanks!
==
I am having some problems with user-defined functions in version 7.3. The
planner se
> > It isn't, but those working on -advocacy were asked to help come up with
a
> > stronger release *announcement* then we've had in the past ...
>
> Consider that a failed experiment. PostgreSQL is driven by the
> development group and, to some extent, by the existing user base. The
> last thing
Neil Conway wrote:
> On Wed, 2002-12-04 at 13:11, Bruce Momjian wrote:
> > Seems I did forget. I always update the minor for a major release, but
> > when development starts, and I seem to have forgotten for 7.3. Sorry.
> >
> > I will update for 7.4 now. Too late for 7.3 clearly.
>
> Wouldn't
On Wed, 2002-12-04 at 13:11, Bruce Momjian wrote:
> Seems I did forget. I always update the minor for a major release, but
> when development starts, and I seem to have forgotten for 7.3. Sorry.
>
> I will update for 7.4 now. Too late for 7.3 clearly.
Wouldn't that suggest that libpq in 7.4 an
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > so clearly 7.2 and 7.3 have the same minor version for all interfaces. Bad!
>
> We forgot between 7.0 and 7.1 as well, so it's at least consistent...
Yes, seems we increament on every even-numbered release. ;-)
--
Bruce Momjian
Peter Eisentraut wrote:
> Marc G. Fournier writes:
>
> > It isn't, but those working on -advocacy were asked to help come up with a
> > stronger release *announcement* then we've had in the past ...
>
> Consider that a failed experiment. PostgreSQL is driven by the
> development group and, to so
Marc G. Fournier writes:
> It isn't, but those working on -advocacy were asked to help come up with a
> stronger release *announcement* then we've had in the past ...
Consider that a failed experiment. PostgreSQL is driven by the
development group and, to some extent, by the existing user base.
Bruce Momjian writes:
> so clearly 7.2 and 7.3 have the same minor version for all interfaces. Bad!
We forgot between 7.0 and 7.1 as well, so it's at least consistent...
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: Ha
Tomas Berndtsson <[EMAIL PROTECTED]> writes:
> After it tries again, it always gets error from recv() for some reason
> that I don't know. I also don't understand why errno is set to ENOTTY
> at this point, that makes no sense at all.
Are you sure it is set? Try setting errno=0 just before recv()
Tom Lane <[EMAIL PROTECTED]> writes:
> Tomas Berndtsson <[EMAIL PROTECTED]> writes:
> > However, after some semi-random looking through the source code of
> > libpq, I tried to change a value, namely here:
> > fe-misc.c row 510 in pqReadData():
> > if (conn->inEnd > 32768 &&
> >
Christopher Kings-Lynne <[EMAIL PROTECTED]> wrote:
> Hi guys,
>
> Just out of interest, if someone was going to pay you to hack on Postgres
> for 6 months, what would you like to code for 7.4?
Well, on top of the oft-requested replication support and savepoint
support, I'd like to see UPDATE, er,
transatlantic=# select '23:59:59.72'::time(0) without time zone;
time
--
24:00:00
(1 row)
So dumping a table with times derived from the timestamp then fails on the
reload with:
psql:transatlantic.dat:43681: ERROR: copy: line 5818, Bad time external
representation '24:00:00'
psql
Tomas Berndtsson <[EMAIL PROTECTED]> writes:
> However, after some semi-random looking through the source code of
> libpq, I tried to change a value, namely here:
> fe-misc.c row 510 in pqReadData():
> if (conn->inEnd > 32768 &&
> (conn->inBufSize - conn->inE
Patrick Welche <[EMAIL PROTECTED]> writes:
> (geometry fails just because of the ordering of the rows in "twenty")
Yeah, that one's my fault. I will fix it soon.
regards, tom lane
---(end of broadcast)---
TIP 6: Have you se
Robert Treat <[EMAIL PROTECTED]> writes:
> Forgive me for not digging through the source code myself, but can
> anyone tell me if setQuerySnapshot behavior within functions was changed
> in 7.3 so that subsequent select statements can see committed data?
AFAIR, we had some preliminary discussions
Tom Lane <[EMAIL PROTECTED]> writes:
> Tomas Berndtsson <[EMAIL PROTECTED]> writes:
> > Yep, there is only one installation of PostgreSQL on the machine. My
> > application is multithreaded, and I have been very careful to open a
> > new connection for each thread. Could it have anything to do wit
Tomas Berndtsson <[EMAIL PROTECTED]> writes:
> Yep, there is only one installation of PostgreSQL on the machine. My
> application is multithreaded, and I have been very careful to open a
> new connection for each thread. Could it have anything to do with
> semaphores and shared memory in Solaris?
On Wed, 4 Dec 2002, Bruce Momjian wrote:
> Marc G. Fournier wrote:
> > On Wed, 4 Dec 2002, Vince Vielhaber wrote:
> >
> > > That wasn't stronger, it was fluffier. It was full of buzzwords that
> > > were masking the actual content. Are you trying to hide the
> > > accomplishments or promote them
Hannu Krosing wrote:
Except that I had to tweak the startup script -
as distributed it defines the version to be 7.3b2 and checks database for version 7.2.
It also expects/puts the database in nonstandard place.
Oops! That's why it is the unofficial RPM set ;-)
FWIW, I produced a new set that
Manfred Koizar wrote:
> [Sorry for the delay. I'm a bit busy these days.]
>
> On Fri, 29 Nov 2002 15:57:17 -0500 (EST), Bruce Momjian
> <[EMAIL PROTECTED]> wrote:
> >> BTW, I think this *forces* us to replace the sub xid with the
> >> respective main xid in a tuple header, when we set
> >> XMIN/M
I must have had an old object file in the build tree... It's all happy
now.
Sorry for the noise,
Patrick
(geometry fails just because of the ordering of the rows in "twenty")
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to
Oliver Elphick wrote:
> On Wed, 2002-12-04 at 12:29, raja kumar thatte wrote:
> > Hai friends,
> > I have a sequence called raj_seq with max value 3000.
> ...
> > now i wanted to increase the max value of the raj_seq
> > to 999.
> > How to do this change?
> > If i drop and recreate the raj_seq,
(gdb) print *((HashJoin *) node)->hashjoinstate
$4 = {jstate = {type = T_HashJoinState, cs_OuterTupleSlot = 0x0,
cs_ResultTupleSlot = 0x84527cc, cs_ExprContext = 0x8453e60,
cs_ProjInfo = 0x84546e0, cs_TupFromTlist = 0 '\000'}, hj_HashTable = 0x0,
hj_CurBucketNo = 0, hj_CurTuple = 0x0,
Just tried a make runcheck with source from Dec 4 15:13 GMT, and:
Core was generated by `postgres'.
Program terminated with signal 11, Segmentation fault.
#0 ExecGetTupType (node=0x8453978) at execProcnode.c:744
744 slot =
hashjoinstate->jstate.cs_ResultTuple
Tom Lane wrote:
> Lee Kindness <[EMAIL PROTECTED]> writes:
> > Perhaps the .so name should have been updated for PostgreSQL 7.3?
>
> It should have been. If it wasn't, that was a serious oversight.
> Not sure if we should change it in 7.3.1 or not, though; it may be
> too late for that. Any thou
On Wed, 4 Dec 2002, Bruce Momjian wrote:
> Marc G. Fournier wrote:
> > On Wed, 4 Dec 2002, Vince Vielhaber wrote:
> >
> > > That wasn't stronger, it was fluffier. It was full of buzzwords that
> > > were masking the actual content. Are you trying to hide the
> > > accomplishments or promote them
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.
---
Teodor Sigaev wrote:
> Thank you very muc
Marc G. Fournier wrote:
> On Wed, 4 Dec 2002, Vince Vielhaber wrote:
>
> > That wasn't stronger, it was fluffier. It was full of buzzwords that
> > were masking the actual content. Are you trying to hide the
> > accomplishments or promote them? If you're trying to hide them like in
> > this ann
On Wed, 2002-12-04 at 12:22, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> >> cms=# CREATE TABLE foo(bar int);
> >> CREATE
> >> cms=# SELECT * from foo where bar=1.7;
>
> > This is a numeric to integer coercion, which rounds
>
> No, it's an integer to numeric promotion (the var is pr
On Wed, 2002-12-04 at 17:33, Dustin Sallings wrote:
> What's wrong with this:
>
> dustin=# create sequence test_seq;
> CREATE SEQUENCE
> dustin=# select nextval('test_seq');
> nextval
> -
>1
> (1 row)
>
> dustin=# select setval('test_seq', );
> setval
>
>9
Around 12:44 on Dec 4, 2002, Joel Burton said:
# The thread here is about how to raise the *max* value for the sequence,
# not how to set the current value higher. The sequence in question was
# created with a too-low maximum value (see help on CREATE SEQUENCE for
# options); the user now wants to
On Wed, Dec 04, 2002 at 09:33:52AM -0800, Dustin Sallings wrote:
> Around 20:41 on Dec 4, 2002, Hannu Krosing said:
>
> What's wrong with this:
>
> dustin=# create sequence test_seq;
> CREATE SEQUENCE
> dustin=# select nextval('test_seq');
> nextval
> -
>1
> (1 row)
>
> du
Around 20:41 on Dec 4, 2002, Hannu Krosing said:
What's wrong with this:
dustin=# create sequence test_seq;
CREATE SEQUENCE
dustin=# select nextval('test_seq');
nextval
-
1
(1 row)
dustin=# select setval('test_seq', );
setval
(1 row)
dustin=# select
Tom Lane <[EMAIL PROTECTED]> writes:
> Tomas Berndtsson <[EMAIL PROTECTED]> writes:
> > Since it works in psql, it must be possible for my application to work
> > too, but I just can't figure out why it doesn't.
>
> I think it's got to be a bug in your application code.
>
> A bug in libpq is the
On Wed, 4 Dec 2002, Tom Lane wrote:
> "Dave Page" <[EMAIL PROTECTED]> writes:
> > I'll preempt the 'this was all discussed on -advocacy, you should have
> > been there' response with yet another agreement with Vince :-) - I too
> > am getting far too much mail these days and another list is the la
On Wed, 4 Dec 2002, Vince Vielhaber wrote:
> I have a new design for it, now it's just getting the time to implement
> it. It's easy to add to and looks alot nicer.
Cool, I think the only beef I ever had with it was the way the results
were presented, but loved teh whole annotated aspects ...
On Wed, 4 Dec 2002, Vince Vielhaber wrote:
> That wasn't stronger, it was fluffier. It was full of buzzwords that
> were masking the actual content. Are you trying to hide the
> accomplishments or promote them? If you're trying to hide them like in
> this announcement you may want to try using
Rod Taylor <[EMAIL PROTECTED]> writes:
>> cms=# CREATE TABLE foo(bar int);
>> CREATE
>> cms=# SELECT * from foo where bar=1.7;
> This is a numeric to integer coercion, which rounds
No, it's an integer to numeric promotion (the var is promoted, not the
constant). Obviously the '=' can never retur
Forgive me for not digging through the source code myself, but can
anyone tell me if setQuerySnapshot behavior within functions was changed
in 7.3 so that subsequent select statements can see committed data? I
know there was some talk about changing the behavior, but I'm wondering
if it was ever d
Lee Kindness <[EMAIL PROTECTED]> writes:
> Perhaps the .so name should have been updated for PostgreSQL 7.3?
It should have been. If it wasn't, that was a serious oversight.
Not sure if we should change it in 7.3.1 or not, though; it may be
too late for that. Any thoughts out there?
Tomas Berndtsson <[EMAIL PROTECTED]> writes:
> Since it works in psql, it must be possible for my application to work
> too, but I just can't figure out why it doesn't.
I think it's got to be a bug in your application code.
A bug in libpq is the only other possibility --- but seeing that psql
als
[Sorry for the delay. I'm a bit busy these days.]
On Fri, 29 Nov 2002 15:57:17 -0500 (EST), Bruce Momjian
<[EMAIL PROTECTED]> wrote:
>> BTW, I think this *forces* us to replace the sub xid with the
>> respective main xid in a tuple header, when we set
>> XMIN/MAX_IS_COMMITTED. Otherwise we'd hav
Perhaps the .so name should have been updated for PostgreSQL 7.3? For
example in 7.2 libpq is:
/usr/lib/libpq.so -> libpq.so.2.2
/usr/lib/libpq.so.2 -> libpq.so.2.2
/usr/lib/libpq.so.2.0 -> libpq.so.2
/usr/lib/libpq.so.2.2
and PostgreSQL 7.3:
/usr/lib/libpq.so -> libpq.so.2.2
On Wed, 2002-12-04 at 11:21, Mario Weilguni wrote:
> I noticed an interesting difference in query behaviour:
>
> cms=# CREATE TABLE foo(bar int);
> CREATE
> cms=# SELECT * from foo where bar=1.7;
This is a numeric to integer coercion, which rounds
rbt=# select 1.7::int;
int4
--
2
(1 ro
"Dave Page" <[EMAIL PROTECTED]> writes:
> I'll preempt the 'this was all discussed on -advocacy, you should have
> been there' response with yet another agreement with Vince :-) - I too
> am getting far too much mail these days and another list is the last
> thing I need.
I'm not subscribed to -ad
"Jeroen T. Vermeulen" <[EMAIL PROTECTED]> writes:
> When receiving a trigger notification under 7.3, the structure returned
> by PQnotifies() appears to be bogus. In a test I ran, its be_pid was
> consistently zero and its relname pointed into never-neverland.
We changed the PQnotifies result str
I noticed an interesting difference in query behaviour:
cms=# CREATE TABLE foo(bar int);
CREATE
cms=# SELECT * from foo where bar=1.7;
bar
-
(0 rows)
cms=# SELECT * from foo where bar='1.7';
ERROR: pg_atoi: error in "1.7": can't parse ".7"
Is this the same problem as index usage with/witho
On Wed, 2002-12-04 at 09:06, Oliver Elphick wrote:
> On Wed, 2002-12-04 at 12:29, raja kumar thatte wrote:
> > Hai friends,
> > I have a sequence called raj_seq with max value 3000.
> ...
> > now i wanted to increase the max value of the raj_seq
> > to 999.
> > How to do this change?
> > If i d
Shridhar Daithankar kirjutas K, 04.12.2002 kell 20:51:
> On 4 Dec 2002 at 20:41, Hannu Krosing wrote:
> > hannu=# update seq set max_value = 99;
> > ERROR: You can't change sequence relation seq
> > hannu=# update pg_class set relkind = 'r' where relname = 'seq';
> > UPDATE 1
> > hannu=# update se
On 4 Dec 2002 at 20:41, Hannu Krosing wrote:
> hannu=# update seq set max_value = 99;
> ERROR: You can't change sequence relation seq
> hannu=# update pg_class set relkind = 'r' where relname = 'seq';
> UPDATE 1
> hannu=# update seq set max_value = 99;
> UPDATE 1
> hannu=# update pg_class set relk
Oliver Elphick kirjutas K, 04.12.2002 kell 19:06:
> On Wed, 2002-12-04 at 12:29, raja kumar thatte wrote:
> > Hai friends,
> > I have a sequence called raj_seq with max value 3000.
> ...
> > now i wanted to increase the max value of the raj_seq
> > to 999.
> > How to do this change?
> > If i dr
Hi, I've been trying to ask on general, and tried to search the
archives without much result, so I'll try here.
I'm using PostgreSQL 7.2.1 on Solaris 8/sparc. In a table, I have a
text field, which may contain long ascii strings. However, when trying
to put data larger than about 32000 characters
Marc G. Fournier kirjutas K, 04.12.2002 kell 18:57:
> On Tue, 3 Dec 2002, Christopher Kings-Lynne wrote:
>
> > Not that anyone cares, but I notice in the commit logs for MySQL 4.1, it
> > now has subselects.
Any idea _where_ you can use them ?
i.e.is it
select a, (select b from tb) from ta;
or
On Wed, 2002-12-04 at 12:29, raja kumar thatte wrote:
> Hai friends,
> I have a sequence called raj_seq with max value 3000.
...
> now i wanted to increase the max value of the raj_seq
> to 999.
> How to do this change?
> If i drop and recreate the raj_seq, then i have to
> recreate the table a
On Wed, 4 Dec 2002, Marc G. Fournier wrote:
> On Wed, 4 Dec 2002, Dave Page wrote:
>
> > I'll preempt the 'this was all discussed on -advocacy, you should have
> > been there' response with yet another agreement with Vince :-) - I too
> > am getting far too much mail these days and another list is
Greg Stark <[EMAIL PROTECTED]> writes:
> Really it boils down to one point: there's really no reason to assume a user
> should be able to execute any new query he feels like. Creating a new query
> should be privileged operation just like creating a new table or new database.
This is an interestin
> -Original Message-
> From: Marc G. Fournier [mailto:[EMAIL PROTECTED]]
> Sent: 04 December 2002 13:56
> To: Dave Page
> Cc: Peter Eisentraut; Justin Clift; Bruce Momjian;
> PostgreSQL-development
> Subject: RE: [HACKERS] [GENERAL] PostgreSQL Global
> Development Group Announces
>
>
On Wed, 4 Dec 2002, Marc G. Fournier wrote:
> On Wed, 4 Dec 2002, Peter Eisentraut wrote:
>
> > Justin Clift writes:
> >
> > > Of course we are, it's just that we're also trying to direct people to
> > > the Advocacy site where there is a lot more info, in a lot more languages.
> >
> > Why don't w
On Tue, 3 Dec 2002, Christopher Kings-Lynne wrote:
> Not that anyone cares, but I notice in the commit logs for MySQL 4.1, it
> now has subselects.
Any idea of which database you have to compile with MySQL to get that
functionality? You aren't saying they actually did something for
themselves th
On Wed, 4 Dec 2002, Dave Page wrote:
> > And I'll pre-empt *that* with "the volume of email isn't
> > changing, only the ability to filter that email" ... the
> > purpose of the -advocacy list is to focus on how to better
> > market the software ... not through stuff like advertising,
> > but how
> -Original Message-
> From: Marc G. Fournier [mailto:[EMAIL PROTECTED]]
> Sent: 04 December 2002 13:41
> To: Dave Page
> Cc: Peter Eisentraut; Justin Clift; Bruce Momjian;
> PostgreSQL-development
> Subject: RE: [HACKERS] [GENERAL] PostgreSQL Global
> Development Group Announces
>
>
On Wed, 4 Dec 2002, Marc G. Fournier wrote:
> On Wed, 4 Dec 2002, Peter Eisentraut wrote:
>
> > Marc G. Fournier writes:
> >
> > > Yup, as with doing anything for the firs ttime, the press release itself
> > > had its 'bugs' ... considering how many times Josh asked for comments on
> > > it, I'm s
Marc G. Fournier wrote:
So as to not recreate the wheel, or, at least, get the wheel properly
rolling, can we get that download page redirected to the one that does
list the mirrors? :)
Yep.
Would the best way to do this be changing the wording to say something like:
"PostgreSQL can be downlo
On Wed, 4 Dec 2002, Marc G. Fournier wrote:
> On Tue, 3 Dec 2002, Vince Vielhaber wrote:
>
> > > Yup, as with doing anything for the firs ttime, the press release itself
> > > had its 'bugs' ... considering how many times Josh asked for comments on
> > > it, I'm surprised that nobody picked up on
On Wed, 4 Dec 2002, Dave Page wrote:
> I'll preempt the 'this was all discussed on -advocacy, you should have
> been there' response with yet another agreement with Vince :-) - I too
> am getting far too much mail these days and another list is the last
> thing I need.
And I'll pre-empt *that* wi
On Wed, 4 Dec 2002, Peter Eisentraut wrote:
> Justin Clift writes:
>
> > Of course we are, it's just that we're also trying to direct people to
> > the Advocacy site where there is a lot more info, in a lot more languages.
>
> Why don't we just shut down the regular web site. Clearly it's not
> c
On Wed, 4 Dec 2002, Justin Clift wrote:
> Dave Page wrote:
>
> > I could have sworn we used to have a bunch of ftp mirrors for downloads.
> > Come to think of it I rewrote/stole a load of Vince's PHP code to allow
> > you to select one from the portal recently. Are we not using them
> > anymore?
On Wed, 4 Dec 2002, Peter Eisentraut wrote:
> Marc G. Fournier writes:
>
> > Yup, as with doing anything for the firs ttime, the press release itself
> > had its 'bugs' ... considering how many times Josh asked for comments on
> > it, I'm surprised that nobody picked up on it *shrug*
>
> And how s
On Tue, 3 Dec 2002, Vince Vielhaber wrote:
> > Yup, as with doing anything for the firs ttime, the press release itself
> > had its 'bugs' ... considering how many times Josh asked for comments on
> > it, I'm surprised that nobody picked up on it *shrug*
>
> I understood it was intentional so comm
> -Original Message-
> From: Justin Clift [mailto:[EMAIL PROTECTED]]
> Sent: 04 December 2002 10:59
> To: Dave Page
> Cc: Peter Eisentraut; Marc G. Fournier; Bruce Momjian;
> PostgreSQL-development
> Subject: Re: [HACKERS] [GENERAL] PostgreSQL Global
> Development Group Announces
>
>
Hi everyone,
We just received this message through the contact form on the Advocacy site.
Thought it would be nice to hear.
:-)
(btw Ajay, you're probably best to upgrade to PostgreSQL 7.2.3 or 7.3
[just released], as 7.2.1 had a few nasty bugs in it)
Regards and best wishes,
Justin Clift
Dave Page wrote:
Strangely I was just thinking the same thing. If all the info is on
advocacy, then what exactly will be left on the main site? Idocs?
Good point, and worth thinking about then.
I was sort of under the impression that the site reshuffle was happening
in a top down manner anywa
On Mon, 2002-12-02 at 23:59, Joe Conway wrote:
> I've hacked the spec file from a 7.2.x source RPM to produce a 7.3 source RPM.
> I've also created a set of i686 binary RPMs. These are *not* official PGDG
> RPMs, and I'm not an RPM expert by any means (so use at your own risk!), but
> I've poste
- Original Message -
From: "Kevin Brown" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, December 03, 2002 8:49 PM
Subject: [mail] Re: [HACKERS] 7.4 Wishlist
> Al Sutton wrote:
> > Point to Point and Broadcast replication
> >
> > With p
Thanks to Rod Taylor's kind help in donating a system account, I've been
able to test libpqxx against postgres 7.3. Unfortunately, I'm running
into several problems. One thing that broke libpqxx was a change in
cursor behaviour that according to Sigurdur Gunnlaugsson seems to be
gone in the 7.4
Thank you very much, you catch it :). This bug had a long life, because it
exists if and only if locale of postmaster
was a different from C (or ru_RU.KOI8-R).
Please, apply patch for current CVS & 7.3.1
Magnus Naeslund(f) wrote:
Ok, I nailed the bug, but i'm not sure what the correct fix is.
At
> -Original Message-
> From: Peter Eisentraut [mailto:[EMAIL PROTECTED]]
> Sent: 03 December 2002 23:34
> To: Justin Clift
> Cc: Dave Page; Marc G. Fournier; Bruce Momjian; PostgreSQL-development
> Subject: Re: [HACKERS] [GENERAL] PostgreSQL Global
> Development Group Announces
>
>
>
On Wed, Dec 04, 2002 at 12:22:41AM +, Sigurdur Gunnlaugsson wrote:
>
> test=# move -10 in test_c;
> MOVE 4
> test=# fetch 1 from test_c;
> schemaname | tablename | tableowner | hasindexes | hasrules | hastriggers
> +---+++--+-
>
94 matches
Mail list logo
