Bruce Momjian <[EMAIL PROTECTED]> writes:
> I am confused about this patch. I don't see extra_float_digits defined
> anywhere. Am I missing a patch?
Evidently. I have the patch and was planning to apply it myself as soon
as Pedro does something with the geometry types...
This has been saved for the 7.4 release:
http:/momjian.postgresql.org/cgi-bin/pgpatches2
I will not apply the _inline_ part.
---
Billy G. Allie wrote:
-- Start of PGP signed section.
> I am including a set of 4 sma
OK, Steve's vote is enough to indicate that most want to wait for
PeerDirect's version before moving forward with the Win32 port.
This also confirms that this will _not_ be an abreviated release cycle
but a full 4-6 months of development, followed by 2 months of beta.
--
I am confused about this patch. I don't see extra_float_digits defined
anywhere. Am I missing a patch?
---
Pedro M. Ferreira wrote:
> Pedro M. Ferreira wrote:
> > Tom Lane wrote:
> >> Perhaps P_MAXLEN now needs to be (2*(D
Hello Katie,
Thursday, November 7, 2002, 7:08:20 PM, you wrote:
KW> Hi, all.
KW> I just wanted to give you an update on where my company (PeerDirect) is with
KW> regards to our native Windows port.
KW> We are planning on contributing the code for the native port sometime next
KW> month (in Dece
Added to TODO:
* Research interaction of setitimer() and sleep() used by statement_timeout
---
Tom Lane wrote:
> I've been trying to do some code review of the recent statement-timeout
> feature addition, and I've got some
Added to TODO:
* Add GUC variables extra_float_digits and extra_double_digits
to control output digits
---
Tom Lane wrote:
> "Pedro M. Ferreira" <[EMAIL PROTECTED]> writes:
> > Have two parameters, say DOUBL
Billy, so your rpath changes are for handling customization you made to
your OS. Sounds like a feature addition to me, which will go into 7.4
only.
---
Billy G. Allie wrote:
-- Start of PGP signed section.
> Larry Rosenman
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > I am fine with this because it only touches unixware-specific stuff,
>
> This is an entirely new feature, so it's inappropriate to do now. And if
> we do it, we should do it for all platforms.
I disagree that it's a new feature. The code to
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> Also, what about if the two servers get the 'begin' command at marginally
> different times, then even:
>
> INSERT INTO foo VALUES (CURRENT_TIMESTAMP);
>
> Will be different on each different machine.
Yeah -- and gettimeofday() will be inco
Larry Rosenman wrote:
> Tom Lane <[EMAIL PROTECTED]> wrote:
> > Larry Rosenman <[EMAIL PROTECTED]> writes:
> >> I don't believe your changes are necessary.
> >
> > The static-inline change was obsoleted by a recent fix, per discussion.
> > But the rpath changes seem possibly useful (or maybe my tho
> "Mikheev, Vadim" <[EMAIL PROTECTED]> writes:
> > > My presumption would be that if you initialize 2 databases to
> > > a known identical start, have all the same triggers and rules
> > > on both, then send all queries to both databases, you will
> > > have 2 identical databases at the end.
> >
>
Turn
on query monitoring in the postgresql.conf and then go:
select
* from pg_stat_activity;
Chris
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Osvâneo A.
FerreiraSent: Wednesday, 6 November 2002 4:49 AMTo:
[EMAIL PROTECTED]Subject
> Is exists patch for 7.4devel ?
A full tarball is based on 7.3devel.
There is no patch for 7.4devel.
http://snaga.org/pgsql/
--
NAGAYASU Satoshi <[EMAIL PROTECTED]>
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Thomas Lockhart <[EMAIL PROTECTED]> writes:
> I'd suggest contributing what you have now. Waiting just keeps others
> from contributing to the topic (which is not your intention certainly,
> but it would have that effect).
Right -- all the work I've done on the topic has been submitted to
Bruce. I
I concur, but do we have some sort of commitment that the rest of
the SQL200x sequence machinery will be supported eventually? Otherwise,
adding some irrelevant syntax variations in limited places doesn't seem
fruitful.
Yes, I'll implement the rest of the SQL200x sequence stuff
eventually. Howeve
Stephan Szabo <[EMAIL PROTECTED]> writes:
> On 7 Nov 2002, Neil Conway wrote:
> > If you have declared the function to return void, then the expression
> > can be omitted, and will be ignored in any case.
>
> I'm not sure how you translated the above to return is optional. I'd
> read it as the
On 7 Nov 2002, Neil Conway wrote:
> The 7.3 docs for the PL/PgSQL return statement say:
>
> RETURN with an expression is used to return from a PL/pgSQL function
> that does not return a set.
>
> [...]
>
> If you have declared the function to return void, then the expression
> can be omitted,
The 7.3 docs for the PL/PgSQL return statement say:
RETURN with an expression is used to return from a PL/pgSQL function
that does not return a set.
[...]
If you have declared the function to return void, then the expression
can be omitted, and will be ignored in any case.
However, that doe
OK, I'll try and do up a diff to B5's tonite (probably late, my Daughter's
elementary school honors choir has a performance tonite).
LER
--On Thursday, November 07, 2002 17:44:37 -0500 Bruce Momjian
<[EMAIL PROTECTED]> wrote:
His updates deal only with the LDLIBRARY path issue, which I think
His updates deal only with the LDLIBRARY path issue, which I think we
are keeping for 7.4:
*** ./doc/FAQ_SCO.orig Wed Nov 6 21:35:46 2002
--- ./doc/FAQ_SCO Wed Nov 6 21:40:44 2002
***
*** 71,76
--- 71,79
configure --with-libs=/usr/local/lib --with-includes=/usr
With or withou Billie's update(s)?
(I haven't looked at them)
LER
--On Thursday, November 07, 2002 17:08:04 -0500 Bruce Momjian
<[EMAIL PROTECTED]> wrote:
We do point to the FAQ_SCO file for specifics. Would you send a diff
for that file?
---
We do point to the FAQ_SCO file for specifics. Would you send a diff
for that file?
---
Larry Rosenman wrote:
> For compilers earlier than the one released with OpenUNIX 8.0.0(UnixWare
> 7.1.2), Including
> the 7.1.1b Feat
Hi, all.
I just wanted to give you an update on where my company (PeerDirect) is with
regards to our native Windows port.
We are planning on contributing the code for the native port sometime next
month (in December). We would have liked to contribute it earlier, but our
work schedules here didn
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> I concur, but do we have some sort of commitment that the rest of
> the SQL200x sequence machinery will be supported eventually? Otherwise,
> adding some irrelevant syntax variations in limited places doesn't seem
> fruitful.
Yes, I'll implement the
On Thursday 07 November 2002 09:50 pm, korry wrote:
> > > b) Send a decoded version of atttypmod - specifically, decode the
> > > precision and scale for numeric types.
> >
> >I want decode type,length,precision and scale
>
> Type is returned by PQftype(), length is returned by PQfsize(). Precisi
> b) Send a decoded version of atttypmod - specifically, decode the
> precision and scale for numeric types.
>
I want decode type,length,precision and scale
Type is returned by PQftype(), length is returned by PQfsize(). Precision
and scale are encoded in the return value from PQfmod() and y
For compilers earlier than the one released with OpenUNIX 8.0.0(UnixWare
7.1.2), Including
the 7.1.1b Feature Supplement, you may need to specify -Xb in CFLAGS or the
CC environment
variable.
--On Thursday, November 07, 2002 16:34:12 -0500 Tom Lane
<[EMAIL PROTECTED]> wrote:
Larry Rosenman <
Larry Rosenman <[EMAIL PROTECTED]> writes:
> It DOES compile out of the box now on 8.0.0(7.1.2) and 7.1.3. Apparently a
> compiler
> fix between the 7.1.1b FS and 7.1.2.
Well, this is what the REMARKS column is for in the supported-platform
list. Seems we need a comment like "for older compiler
> b) Send a decoded version of atttypmod - specifically, decode the
> precision and scale for numeric types.
>
I want decode type,length,precision and scale
regards
Haris Peco
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Dave Miller ([EMAIL PROTECTED]) tells me this bug is fixed in gcc 3.2.1
(which does not appear to be distributed yet). FYI.
alex
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command
--On Thursday, November 07, 2002 22:21:56 +0100 Peter Eisentraut
<[EMAIL PROTECTED]> wrote:
Olivier PRENANT writes:
I don't mind having CFLAGS=-Xb though, done it for php already...
By everyone says this should go off so..
The idea of the platform testing is not to determine whether you ca
Bruce Momjian writes:
> I am fine with this because it only touches unixware-specific stuff,
This is an entirely new feature, so it's inappropriate to do now. And if
we do it, we should do it for all platforms.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadc
Olivier PRENANT writes:
> I don't mind having CFLAGS=-Xb though, done it for php already...
> By everyone says this should go off so..
The idea of the platform testing is not to determine whether you can
compile PostgreSQL after performing a secret dance. If it doesn't compile
with the default
Neil Conway writes:
> Last I heard, we had concluded that SQL2003's notion of a sequence is
> sufficiently close to ours that the differences are mostly syntax.
I concur, but do we have some sort of commitment that the rest of
the SQL200x sequence machinery will be supported eventually? Otherwis
Serguei Mokhov writes:
> Can I still send in translation patches so that they
> get into 7.4 or is it too late already? If it's not
> late, what would be the 'deadline' then?
Send them rather soon.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)--
On Thu, Nov 07, 2002 at 13:44:11 -0400,
"Marc G. Fournier" <[EMAIL PROTECTED]> wrote:
>
> I haven't noticed any 'drag' so far this release ... we had a long beta
> between 2 and 3, but 3->4 and 4->5 have been really short (so short that 4
> didn't exist) ...
I managed to be running beta 4 for a
Thomas Lockhart <[EMAIL PROTECTED]> writes:
> What would be required to have OIDs for all SELECT/INTO product tables
> for this release?
It *might* work to just reverse the default assumption in
ExecAssignResultTypeFromTL(). But I will vote against making such a
change at this late hour. Quite
FYI: I easily updated to 1.75 and all is well.
Thanks for all the help,
L.
On Thu, 7 Nov 2002, Tom Lane wrote:
> I said:
> >> It's interesting that bison 1.28's output is sufficiently different to
> >> cause a problem, but we are not going to worry about supporting use of
> >> old bisons.
>
> W
There has been some previous discussion of changing the FE/BE protocol
in 7.4, in order to fix several problems. I think this is worth doing:
if we can resolve all these issues in a single release, it will lessen
the upgrade difficulties for users.
Here are a couple of other changes you might c
I agree with Neil: in many situations it's not reasonable to try to
associate a unique "source table" with a CREATE AS or SELECT INTO, and
therefore automatically propagating hasoids is doomed to failure.
Well, it certainly is reasonable to have better behavior than currently.
We do something no
Neil Conway <[EMAIL PROTECTED]> writes:
> Unless we can define some consistent semantics for when we use the
> hasoids of the source table(s), I'd say we should just add the
> WITH/WITHOUT OIDS syntax.
I agree with Neil: in many situations it's not reasonable to try to
associate a unique "source t
How would we make use of 'hasoids' in the case of multiple source
tables, or a source table defined by an SRF?
Choose a convention. At the moment, the first source table provides more
characteristics to the target than do the other sources, and that could
be true for OIDs also. I would be incli
Marc G. Fournier wrote:
> On Thu, 7 Nov 2002, Bruce Momjian wrote:
>
> > I am loosing tolerance for these last-minute changes. We should not
>
> You might be, I'm not ... when we finally release v7.3, it will be *as
> solid* as our previous releases ... *shrug*
All I am saying is that I would l
I said:
> Anyway, get_last_socket_error() seems exactly equivalent to our macro
> SOCK_ERRNO in libpq/libpq-int.h. AFAICT, the uses of it in our
> code are these:
> /home/postgres/pgsql/src/backend/libpq/be-secure.c:
> errno = get_last_socket_error();
> /home/postgres/pgsql/src/backend/libpq/be-s
On Thu, Nov 07, 2002 at 01:44:21PM -0500, Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > On Thu, Nov 07, 2002 at 12:27:05AM -0500, Tom Lane wrote:
> >> CLUSTER ALL patch: I have a problem with this, specifically the fact
> >> that it changes CLUSTER into a multi-transaction operat
Thomas Lockhart <[EMAIL PROTECTED]> writes:
> ... and the same for SELECT/INTO Also, the hasoids (or equivalent)
> attribute is not picked up from the source table which would be
> another way to push this property into the target table.
How would we make use of 'hasoids' in the case of multiple s
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> On Thu, Nov 07, 2002 at 12:27:05AM -0500, Tom Lane wrote:
>> CLUSTER ALL patch: I have a problem with this, specifically the fact
>> that it changes CLUSTER into a multi-transaction operation.
> That was your suggestion...
Well, it'd be okay (IMHO anyw
On Thu, Nov 07, 2002 at 12:27:05AM -0500, Tom Lane wrote:
> CLUSTER ALL patch: I have a problem with this, specifically the fact
> that it changes CLUSTER into a multi-transaction operation.
That was your suggestion...
> That renders CLUSTER non-rollbackable and not callable from functions.
> Af
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> I'm guessing that what we need to do is -D_GNU_SOURCE somewhere in the
>> Makefiles; the $64 question is exactly where
> The simplest choice would be to just define it unconditionally in linux.h.
> Since it is not supposed to chang
On Thu, 7 Nov 2002, Bruce Momjian wrote:
> Tom Lane wrote:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > I am loosing tolerance for these last-minute changes. We should not
> > > hold up release to support some obscure platform.
> >
> > As long as the docs are unfinished, I don't feel any p
On Thu, 7 Nov 2002, Bruce Momjian wrote:
> I am loosing tolerance for these last-minute changes. We should not
You might be, I'm not ... when we finally release v7.3, it will be *as
solid* as our previous releases ... *shrug*
---(end of broadcast)---
On Thu, 7 Nov 2002, Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > Tom, my understanding is that CONVERT stuff required an initdb, and was
> > also the only thing 'critical' that went in ... correct? What impact does
> > that have? For instance, could it cause one of the re
Is exists patch for 7.4devel ?
regards
Haris Peco
On Tuesday 05 November 2002 01:14 am, Satoshi Nagayasu wrote:
> Hi all,
>
> Mike Mascari <[EMAIL PROTECTED]> wrote:
> > Is there any thought about changing the protocol to support
> > two-phase commit? Not that 2PC and distributed transactions
> >
--On Thursday, November 07, 2002 18:02:51 +0100 Olivier PRENANT
<[EMAIL PROTECTED]> wrote:
Haha!!!
It passes (b4) on 800 and not on uw 711..
Larry, should I install 800 SDK on 711?
Yes.
On Thu, 7 Nov 2002, Larry Rosenman wrote:
Date: Thu, 07 Nov 2002 10:45:13 -0600
From: Larry Rosenman
On Tue, 5 Nov 2002, Florian Litot wrote:
> what is the command to launch a sql script not in psql
> thanks
without actually being IN psql, you can use it to run one line scripts
like this:
psql dbname -c -- 'single query goes here'
or you can run a large file full of sql queries like this:
ps
Haha!!!
It passes (b4) on 800 and not on uw 711..
Larry, should I install 800 SDK on 711?
On Thu, 7 Nov 2002, Larry Rosenman wrote:
> Date: Thu, 07 Nov 2002 10:45:13 -0600
> From: Larry Rosenman <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Cc: Tom Lane <[EMAIL PROTECTED]>, Billy G. Allie <[EMA
Be more specific with your question, what exactly are You trying to do ?
Did you ment PL/PSQL script (stored procedure) , or You are asking about
interfaces to PostgreSQL ?
I suppose the right place to ask questions like that would be
[EMAIL PROTECTED], not to hackers.
regards !
On Tuesday 05
cc -O -g -I../../../../src/include -I/usr/local/include -c -o tuplesort.o
tuplesort.c
UX:cc: WARNING: debugging and optimization mutually exclusive; -O disabled
It still passes here. I really wonder if they fixed something in the 4.1
compiler. IIRC
the 7.1.1b compiler is 4.0.
Truly wierd.
LE
What's FS, it(s the 7.1.1b compiler yes.
I don't mind having CFLAGS=-Xb though, done it for php already...
By everyone says this should go off so..
Regards
On Thu, 7 Nov 2002, Larry Rosenman wrote:
> Date: Thu, 07 Nov 2002 10:37:36 -0600
> From: Larry Rosenman <[EMAIL PROTECTED]>
> To: [EMAIL
FS== Feature Supplement.
I've got a compile running with the 7.3b5 tarball on my 7.1.3 system (with
the newer
compiler).
We'll see. :-)
--On Thursday, November 07, 2002 17:40:24 +0100 Olivier PRENANT
<[EMAIL PROTECTED]> wrote:
What's FS, it(s the 7.1.1b compiler yes.
I don't mind having C
It **LOOKS** right. I'm about to double check it on 7.1.3.
Olivier, is this the 7.1.1b FS Compiler?
I wonder if a bug fix made it in...
Wierd.
--On Thursday, November 07, 2002 17:34:49 +0100 Olivier PRENANT
<[EMAIL PROTECTED]> wrote:
I see the latter in both b4 and b5!
I've just relaunche
... and the same for SELECT/INTO Also, the hasoids (or equivalent)
attribute is not picked up from the source table which would be another
way to push this property into the target table.
One or both of these mechanisms (I'd think both should be available)
would seem to be required to make thes
I see the latter in both b4 and b5!
I've just relaunched my mirroring procedure and it did'nt pick another b4
or b5!
What happens??
Regards,
On Thu, 7 Nov 2002, Tom Lane wrote:
> Date: Thu, 07 Nov 2002 11:26:42 -0500
> From: Tom Lane <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Cc: Larry Rosen
*WHAT??**
this directory has hust been created by de-taring postgresql-7.3b5.tar.gz
from my own mirror dated nov 6 20:04...
On Thu, 7 Nov 2002, Larry Rosenman wrote:
> Date: Thu, 07 Nov 2002 10:07:37 -0600
> From: Larry Rosenman <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED], Tom Lane <[EMAIL PROT
Olivier PRENANT <[EMAIL PROTECTED]> writes:
> *WHAT??**
> this directory has hust been created by de-taring postgresql-7.3b5.tar.gz
> from my own mirror dated nov 6 20:04...
Well, there's something darn weird here. Is
src/backend/utils/sort/tuplesort.c version 1.28 or 1.29? At line 1838,
do you
I now realize that server_min_messages should have been
log_min_messages. The log_* grouping was done after I added
server_min_messages and I didn't see the similarity. Also,
show_parser_stats, etc. should be log_parser_stats because the output
goes to the log and not to the user's terminal.
I m
> > This is wrong assumption. If
> >
> > 1st client executes UPDATE t SET a = 1 WHERE b = 2;
> > 2nd client executes UPDATE t SET a = 2 WHERE b = 2;
> >
> > at "the same time" you don't know in what order these
> > queries will be executed on two different servers (because
> > you can't control
On Thu, 7 Nov 2002, Tom Lane wrote:
> Date: Thu, 07 Nov 2002 10:21:25 -0500
> From: Tom Lane <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Cc: Larry Rosenman <[EMAIL PROTECTED]>, Billy G. Allie <[EMAIL PROTECTED]>,
> [EMAIL PROTECTED], [EMAIL PROTECTED]
> Subject: Re: [PORTS] [HACKERS] Postgr
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I am loosing tolerance for these last-minute changes. We should not
> hold up release to support some obscure platform.
As long as the docs are unfinished, I don't feel any particular
compunction about not applying portability fixes. If you want RC1
to
It looks like you do **NOT** have B4 or B5
LER
--On Thursday, November 07, 2002 17:00:21 +0100 Olivier PRENANT
<[EMAIL PROTECTED]> wrote:
On Thu, 7 Nov 2002, Tom Lane wrote:
Date: Thu, 07 Nov 2002 10:21:25 -0500
From: Tom Lane <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: Larry Rosenman
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I am loosing tolerance for these last-minute changes. We should not
> > hold up release to support some obscure platform.
>
> As long as the docs are unfinished, I don't feel any particular
> compunction about not applying portabilit
--On Thursday, November 07, 2002 15:44:37 +0100 Olivier PRENANT
<[EMAIL PROTECTED]> wrote:
On Thu, 7 Nov 2002, Larry Rosenman wrote:
Date: Thu, 07 Nov 2002 08:41:58 -0600
From: Larry Rosenman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: Billy G. Allie <[EMAIL PROTECTED]>, [EMAIL PROTECTED],
On Tue, Nov 05, 2002 at 03:19:44PM +0100, Florian Litot wrote:
> what is the command to launch a sql script not in psql
Perl?
Or maybe you just want to read SQL into Postgres using the shell. In
which case, try the -f switch to psql.
A
--
Andrew Sullivan 204-4141
On Thu, 7 Nov 2002, Larry Rosenman wrote:
> Date: Thu, 07 Nov 2002 08:41:58 -0600
> From: Larry Rosenman <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Cc: Billy G. Allie <[EMAIL PROTECTED]>, [EMAIL PROTECTED],
> [EMAIL PROTECTED]
> Subject: Re: [PORTS] [HACKERS] PostgreSQL supported platform
Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > Tom, my understanding is that CONVERT stuff required an initdb, and was
> > also the only thing 'critical' that went in ... correct? What impact does
> > that have? For instance, could it cause one of the regression tests to
> >
On 4 Nov 2002 at 12:23, Mikheev, Vadim wrote:
> > My presumption would be that if you initialize 2 databases to
> > a known identical start, have all the same triggers and rules
> > on both, then send all queries to both databases, you will
> > have 2 identical databases at the end.
>
> This is
Olivier PRENANT <[EMAIL PROTECTED]> writes:
> Huh! I just tried to compile 7.3b5 without CFLAGS=-Xb, it still bugs the
> compiler...
It won't get better if you don't show any details...
regards, tom lane
---(end of broadcast)---
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> Tom, my understanding is that CONVERT stuff required an initdb, and was
> also the only thing 'critical' that went in ... correct? What impact does
> that have? For instance, could it cause one of the regression tests to
> fail, or is it something
=?iso-8859-15?q?Herv=E9=20Piedvache?= <[EMAIL PROTECTED]> writes:
> I don't know if it's important or not ... but on my linux Debian woody, with
> fr_FR@euro parameter when I do the initdb I've got a creating template1
> database in /usr/local/pgsql/data/base/1... Failed to initialize lc_messages
On Tue, Nov 05, 2002 at 06:48:30PM -0200, Osv?neo A. Ferreira wrote:
> Hi,
>
> I has a dinamic application, constructed on php, connecting in db postgres 7.2.
> I would like monitor the all established connection. I want know whish command is
>running at moment.
>
> Help, please !!!
Check out
Achilleus Mantzios <[EMAIL PROTECTED]> writes:
> After recreating the missing triggers should i upgrade
> to 7.2.3??
Make that "before".
I frankly suspect pilot error here. Triggers do not simply disappear.
If you did have crash-induced corruption leading to loss of some rows
in pg_trigger, it w
"Mikheev, Vadim" <[EMAIL PROTECTED]> writes:
> > My presumption would be that if you initialize 2 databases to
> > a known identical start, have all the same triggers and rules
> > on both, then send all queries to both databases, you will
> > have 2 identical databases at the end.
>
> This is wr
--On Thursday, November 07, 2002 14:23:43 +0100 Olivier PRENANT
<[EMAIL PROTECTED]> wrote:
On Thu, 7 Nov 2002, Larry Rosenman wrote:
Date: Thu, 07 Nov 2002 06:41:02 -0600
From: Larry Rosenman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: Billy G. Allie <[EMAIL PROTECTED]>, [EMAIL PROTECTED],
On Thu, 7 Nov 2002, Achilleus Mantzios wrote:
> On Wed, 6 Nov 2002, Stephan Szabo wrote:
>
> > On Wed, 6 Nov 2002, Achilleus Mantzios wrote:
> >
> > >
> > > Hi i think a hit a major problem on 7.2.1.
> > > I run 3 systems with postgresql 7.2.1.
> > > Its a redhat 7.1 for development, a redhat 7.3
On Wed, 6 Nov 2002, Stephan Szabo wrote:
> On Wed, 6 Nov 2002, Achilleus Mantzios wrote:
>
> >
> > Hi i think a hit a major problem on 7.2.1.
> > I run 3 systems with postgresql 7.2.1.
> > Its a redhat 7.1 for development, a redhat 7.3 for production
> > and a FreeBSD 4.6.1RC2 for testing.
> >
> >
Larry Rosenman wrote:
> We already have success messages from Olivier Prenant for 7.3B4 on 8.0.0,
> and me for 7.1.3.
>
> I don't believe your changes are necessary.
>
Was that using gcc or the native compiler?
Was it in linux kernel personality mode or OpenUNIX mode.
I was compiling using the
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I am fine with this because it only touches unixware-specific stuff,
> > except the change to Tom's inline function:
> > [static] inline Datum
> > myFunctionCall2(FmgrInfo *flinfo, Datum arg1, Datum arg2)
> > Tom will have to comme
Tom Lane wrote:
> "Billy G. Allie" <[EMAIL PROTECTED]> writes:
> > Here is the error messages generated during the compile:
>
> > cc -K pentium_pro,host,inline,loop_unroll -I../../../../src/include
> > -I/usr/local/include -I/usr/local/ssl/include -c -o tuplesort.o tuplesort.
> c
> > UX:acomp: E
On Wed, Nov 06, 2002 at 05:02:14PM +0900, Satoshi Nagayasu wrote:
> Hannu Krosing <[EMAIL PROTECTED]> wrote:
> > > Exactly. When user send the COMMIT command to the master server, the
> > > master.talks to the slaves to process precommit-vote-commit using the
> > > 2PC. The 2PC cycle is hidden fro
Also i must that these lost triggers implement the parent table
side of the constraint, e.g.
CREATE TABLE VslSections(
id serial NOT NULL UNIQUE PRIMARY KEY,
name varchar(20) NOT NULL UNIQUE);
CREATE TABLE MachClasses(
id serial NOT NULL UNIQUE PRIMARY KEY,
name varchar(20) NOT NULL UNIQUE,
vslse
I was wrong about parent side triggers only having
disappeared.
Triggers of both sides are missing.
==
Achilleus Mantzios
S/W Engineer
IT dept
Dynacom Tankers Mngmt
Nikis 4, Glyfada
Athens 16610
Greece
tel:+30-10-8981112
fax:
Hi i think a hit a major problem on 7.2.1.
I run 3 systems with postgresql 7.2.1.
Its a redhat 7.1 for development, a redhat 7.3 for production
and a FreeBSD 4.6.1RC2 for testing.
After long runs (with periodic (daily) vacuum analyze's)
i noticed that some of the triggers that implement referenti
According to the feedback I have had, e_os.h is no longer a public interface
header file in OpenSSL. 'get_last_socket_error' is a macro that seems to
expand to errno.
Can I suggest someone with better understanding of the postgresql sources,
and ssl support, please pick this up - maybe in time for
Hi,
I has a dinamic application, constructed on
php, connecting in db postgres 7.2.
I would like monitor the all established
connection. I want know whish command is running at moment.
Help, please !!!
Osvâneo A. Ferreira
[EMAIL PROTECTED]
what is the command to launch a sql script not in psql
thanks
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
> My presumption would be that if you initialize 2 databases to
> a known identical start, have all the same triggers and rules
> on both, then send all queries to both databases, you will
> have 2 identical databases at the end.
This is wrong assumption. If
1st client executes UPDATE t SET a =
Hi all,
Mike Mascari <[EMAIL PROTECTED]> wrote:
> Is there any thought about changing the protocol to support
> two-phase commit? Not that 2PC and distributed transactions
> would be implemented in 7.4, but to prevent another protocol
> change in the future?
I'm now implementing 2PC replicatio
This post is just for closure -- both of the issues below have been
resolved:
On Tue, Oct 29, 2002 at 09:47:35AM -0500, Jason Tishler wrote:
> > > 1. Cygwin bison needs to be upgraded from 1.35 to 1.75 (i.e.,
> > > 1.50+) to process src/interfaces/ecpg/preproc/preproc.y
> > > successfully. I will
On Wed, 6 Nov 2002, Bruce Momjian wrote:
> Marc G. Fournier wrote:
> >
> > News to me ...
> >
> > On Wed, 6 Nov 2002, Bruce Momjian wrote:
> >
> > > Are we still on schedule for RC1 on Friday?
>
> I am asking. We almost got to RC1 last Friday, so I figured we could do
> RC1 this Friday. The chan
1 - 100 of 107 matches
Mail list logo
