"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> Just wondering if someone could give me an indication as to how to create a
> new regression test, for the ADD UNIQUE stuff I did?
It's not hard. Make a file in src/test/regress/sql containing test
queries, and one in src/test/regress/sql/e
Lee Kindness writes:
> COMMIT: AND [NO] CHAIN options? Where do these come from,
> it's not ANSI (i'd probably leave this one).
Sure is.
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
---(end of broadcast)--
In a few hours, vince and I will be shutting down the rsync mirror on
hub.org ... we've been spending the past couple of weeks re-doing and
re-writing *alot* of the sites ...
for instance, if you mirror www.postgresql.org, it no longer includes the
extensive mailing list archives ... that is a s
Try http://techdocs.postgresql.org/
Chris
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Nathan Reilly
> Sent: Tuesday, 16 October 2001 11:31 AM
> To: [EMAIL PROTECTED]
> Subject: [HACKERS] Replication
>
>
> I'm sure this is not the correct plac
On Tue, 16 Oct 2001, Peter Eisentraut wrote:
> Bill Studenmund writes:
>
> > I disagree. Views and tables are the purview of schemas, which as I
> > mentioned to Tom, strike me as being different from packages.
>
> Well, obviously schemas are a namespacing mechanism for tables and views.
> And ap
> I've been looking for documents and other info on replication efforts in
> PostgreSQL. If anyone here can point me to places where I can find
> these, it would be really appreciated.
PostgreSQL Inc offers asynchronous one-way replication, used and proven
in high throughput environments. The ori
Hi All,
Just wondering if someone could give me an indication as to how to create a
new regression test, for the ADD UNIQUE stuff I did?
I intend to do a regression test during the beta, and try to produce a patch
that addresses some of the concerns Tom had with the code.
Cheers,
Chris
-
> I've been looking for documents and other info on replication efforts in
> PostgreSQL. If anyone here can point me to places where I can find
> these, it would be really appreciated.
It really depends on your replication needs. I would suggest taking a
look at gborg.postgresql.org for any of t
Bill Studenmund writes:
> I disagree. Views and tables are the purview of schemas, which as I
> mentioned to Tom, strike me as being different from packages.
Well, obviously schemas are a namespacing mechanism for tables and views.
And apparently the "packages" you propose are (among other thing
known problems, should be fixed and catching up now ...
On Tue, 16 Oct 2001, Tatsuo Ishii wrote:
> I saw over 7 hours delay between postgresql.org and sever1.pgsql.org.
> Does anynone know what's happening here?
>
> Received: from postgresql.org (webmail.postgresql.org [216.126.85.28])
>
>
> I've been looking for documents and other info on replication efforts
> in PostgreSQL. If anyone here can point me to places where I can
> find these, it would be really appreciated.
Here is some research work that was conducted a few months ago.
http://gborg.postgresql.org/genpage?rep
Lee Kindness <[EMAIL PROTECTED]> writes:
> Obviously a new column name will have to be used, however is there a
> definitive list of keywords to avoid so such an occurance wouldn't
> happen in a production system?
There is an up-to-date list of keywords in the documentation:
http://www.ca.postgre
bpalmer <[EMAIL PROTECTED]> writes:
> Did I miss something here?
No, but Marc said yesterday that he and Vince were in process of
changing something about mirror configuration. You'll have to
ask them if mirror admins need to do anything...
regards, tom lane
---
On Tue, 16 Oct 2001, Lee Kindness wrote:
> And the patch below corrects a pet peeve I have with ecpg, all errors
> and warnings are output with a line number one less than reality...
I think this patch is wrong. Wouldn't it be better to make the line number
in yylineno be correct? Also, there ar
On Mon, 15 Oct 2001, Christopher Kings-Lynne wrote:
> Hmmm. I don't know why date_part isn't working, but I now only use the
> EXTRACT syntax for maximum SQL compatibility. ie. Do this instead:
>
> v_seed := EXTRACT (EPOCH FROM CURRENT_TIMESTAMP);
Unfortunatly that gives the same error. I thin
I agree we need to find out why the line number is off rather than
covering up the problem. Patch rejected.
---
> Lee Kindness writes:
> > Patch below, it changes:
> > 1. A number of mmerror(ET_ERROR) to mmerror(ET_NOTI
Patch to be applied to proper config* file.
Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
>
Lee Kindness <[EMAIL PROTECTED]> writes:
> And the patch below corrects a pet peeve I have with ecpg, all errors
> and warnings are output with a line number one less than reality...
Hmm. yylineno *should* be the right thing. I think you are patching
a symptom rather than fixing the correct cau
Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
> Tom Lane writes:
> > Uh, isn't the correct
Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
> Lee Kindness writes:
> > Patch below, it ch
> You can find a snapshot that should be pretty durn close to 7.2beta1
> at ftp://ftp2.us.postgresql.org/pub/dev/postgresql-snapshot.tar.gz
> (note that at last word, other mirrors were not up to date --- if
> the doc/TODO file doesn't contain a date in October, it's stale).
> I think the only thi
I'm sure this is not the correct place to ask this, but:
I've been looking for documents and other info on replication efforts in
PostgreSQL. If anyone here can point me to places where I can find
these, it would be really appreciated.
Also, if any of you have any comments and warnings about
On Mon, 15 Oct 2001, Marc G. Fournier wrote:
>
> try ftp2.us.postgresql.org ... this is what is holding up beta right now,
> we have to get the mirrors fixed, which Vince is working on ...
> ftp2.us.postgresql.org is the only 'operational' mirror we have right now,
> but, since Vince isn't ready
On Tue, 16 Oct 2001, Tom Lane wrote:
> bpalmer <[EMAIL PROTECTED]> writes:
> > Did I miss something here?
>
> No, but Marc said yesterday that he and Vince were in process of
> changing something about mirror configuration. You'll have to
> ask them if mirror admins need to do anything...
They
In moving from 7.1.3 to 7.2devel (for bug fixes) we've encountered a
problem with a, previously valid, column name: time. In 7.1.3 the
following worked:
CREATE TABLE test(time INTEGER);
while in 7.2devel it results in a parse error:
ERROR: parser: parse error at or near "time"
Looking at
Tatsuo Ishii writes:
> I saw over 7 hours delay between postgresql.org and sever1.pgsql.org.
> Does anynone know what's happening here?
I've seen massive delays too:
Received: from mail.csl.co.uk by euphrates.csl.co.uk (8.9.3/ConceptI 2.4)
id EAA08864; Tue, 16 Oct 2001 04:24:41 +0100
Done.
> Ok, here is the modified encoding table (column1 is the standard name,
> 2 is our "official" name, and 3 is alias). If there's no objection, I
> will change them.
>
> ASCII SQL_ASCII
> UTF-8 UNICODE UTF_8
> MULE-INTERNAL MULE_INTERNAL
> ISO-8859-1LATIN1
Hi!
Without this patch I couldn't compile PostgreSQL on Solaris 8 x86 using
Sun's compiler. May be it will be usefull for someone else?
Regards
Denis Ustimenko
Oldham
---
denis@tracer$ diff configure.orig configure
744c744
< i?86-*-s
Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
> Bruce Momjian writes:
> > Lee Kindness writ
I saw over 7 hours delay between postgresql.org and sever1.pgsql.org.
Does anynone know what's happening here?
Received: from postgresql.org (webmail.postgresql.org [216.126.85.28])
by server1.pgsql.org (8.11.6/8.11.6) with ESMTP id f9GBurU27235
for <[EMAIL PROTECTED]>; Tue, 16 Oc
At 10:18 AM 15-10-2001 -0400, Tom Lane wrote:
>Lincoln Yeoh <[EMAIL PROTECTED]> writes:
>> Create a small program that makes a few connections to postgresql, does
>> some initialization, preconnects to various DBs (or maybe limited to one DB
>> specified on startup), and listens on one port/socket
Bruce Momjian writes:
> Lee Kindness writes:
> > In which case a number of other cases should be weeded out of
> > parser.y and passed onto the backend:
> > [ snip ]
> > Let me known if you want a patch for these cases too.
> Sure, send them on over.
Patch below, it changes:
1. A number o
Lee Kindness <[EMAIL PROTECTED]> writes:
> The existing code in ecpg/preproc/preproc.y to handle the WITH option
> simply throws an error and aborts the processing... The patch below
> prevents the segfault and also passes on the WITH option to the
> backend, probably a better fix.
I agree. It s
Vince Vielhaber <[EMAIL PROTECTED]> writes:
> On Mon, 15 Oct 2001, Zeugswetter Andreas SB SD wrote:
>> The http link to the snapshots no longer works on
>> www.ca.postgresql.org/ftpsite.
> It's fixed, but they all point to the same place so I don't see how
> one would work and not the other. The
On Sun, 14 Oct 2001, Peter Eisentraut wrote:
> I have been pondering a little about something I called "package",
> completely independent of anything previously implemented. What I would
> like to get out of a package is the same thing I get out of package
> systems on operating systems, namely
(I'm having trouble with e-mail, so if you get this twice, sorry)
I was looking at some Oracle configuration files today, and it occurred to me
how Postgres can be made to pre-fork, similarly to Oracle.
Oracle has "listener" processes that listen on a port for Oracle clients. The
listeners are c
36 matches
Mail list logo
