The world rejoiced as [EMAIL PROTECTED] ("Gustavo Tonini") wrote:
> Ozsu show us some solution for the problem in the book "Principles of
> distributed database systems".
Would it be "telling" to outline some of the solutions he suggests?
--
(format nil "[EMAIL PROTECTED]" "cbbrowne" "gmail.com")
Michael Fuhr <[EMAIL PROTECTED]> writes:
> Here's a complete test case:
> CREATE TABLE foo (a integer[]);
> INSERT INTO foo (a)
> SELECT array[random() * 10, random() * 10, random() * 10]
> FROM generate_series(1, 24);
> CREATE INDEX foo_a_idx ON foo USING gist (a gist__int_ops);
> SET enab
David Wheeler <[EMAIL PROTECTED]> writes:
> Right, but me, while I compile lots of stuff, I don't understand
> configure or autconf at all. So I was completely unaware of this
> feature. I'm very pleased to know it now, of course. But I don't see
> how it could be any harm to add notes to the
On Apr 1, 2006, at 15:49, Peter Eisentraut wrote:
Well, you got one of them, but I still have my doubts about
"/usr/bin/per5.8.6".
LOL! God, what an oaf!
David
Index: doc/src/sgml/installation.sgml
===
RCS file: /projects/cvsroot
David Wheeler wrote:
> On Apr 1, 2006, at 15:39, David Wheeler wrote:
> > So, pray tell, what have I screwed up? I would of course be happy
> > to submit a corrected patch.
>
> Sorry, I'm an idiot. New version attached.
Well, you got one of them, but I still have my doubts about
"/usr/bin/per5.8.
On Apr 1, 2006, at 15:39, David Wheeler wrote:
So, pray tell, what have I screwed up? I would of course be happy
to submit a corrected patch.
Sorry, I'm an idiot. New version attached.
Best,
David
Index: doc/src/sgml/installation.sgml
===
I run configure (no complains about bison o flex), after a few seconds I receive the next errors: make[4]: Leaving directory `/pgsql/src/backend/access/nbtree'make -C transam SUBSYS.omake[4]: Entering directory `/pgsql/src/backend/access/transam'make[4]: `SUBSYS.o' is up to date.make[4]: Leavin
On Apr 1, 2006, at 06:58, Peter Eisentraut wrote:
Next time you submit a patch, please consider reading it before
sending
it out.
I just read the patch, and it looks fine to me. No typos that I
noticed. I might have screwed up the SGML stuff, but I know even less
about SGML than I do abo
On Mar 31, 2006, at 20:02, Tom Lane wrote:
You can give `configure' initial values for configuration
parameters
by setting variables in the command line or in the environment.
Here
is an example:
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
This isn't super helpful, of course,
[Please copy the mailing list on replies.]
On Sat, Apr 01, 2006 at 07:20:57PM +0200, jeroen van iddekinge wrote:
> > TRAP: BadArgument("!(((header->context) != ((void *)0) &&
> > (Node*)((header->context)))->type) == T_AllocSetContext", File:
> > "mcxt.c", Line: 612)
> >
>
> I started
Ozsu show us some solution for the problem in the book "Principles of
distributed database systems".
On 4/1/06, D'Arcy J.M. Cain wrote:
> On Fri, 31 Mar 2006 17:57:25 -0300
> "Gustavo Tonini" <[EMAIL PROTECTED]> wrote:
> > why there's no way to make multi-master replication generic?
>
> Well, tha
Hi,
On Mar 25 08:47, John DeSoi wrote:
> I have not looked at libpq in any detail, but it should have access
> to the type of all the parameters in the prepared statement. The
> Describe (F) statement in the frontend/backend protocol identifies
> the type of each parameter.
I've prepared a
But there is still no way to verify that the information in the file is
what postgres saw last. DBAs make mistakes too. A simple way to view
the current access state would be much appreciated.
On Apr 1, 2006, at 1:01 PM, Andrew Dunstan wrote:
Er, how can the file be changed behind the scenes
Er, how can the file be changed behind the scenes? Only if you have
opened up permission to the directory to someone else, or you don't
trust your sysadmins.
Either way you would then have much bigger problems than this.
cheers
andrew
Agent M wrote:
Unfortunately, there is still one serio
Unfortunately, there is still one serious deficiency with the solution
below- it may not be the actual information postgresql is currently
using to determine who can log in and how- the file can be easily
changed behind the scenes and there is currently no way to know.
I (speaking as a DBA) wo
On Sat, Apr 01, 2006 at 03:40:19PM +0200, jeroen van iddekinge wrote:
> When using intarray operator in a query, postgres dies and restart
> itself when executing the following query:
>
> select r1.bet_sentence & r2.bet_sentence
> from related r1,related r2
> where r1.bet_sentence && r2.bet_sente
Jim C. Nasby wrote:
On Fri, Mar 31, 2006 at 07:01:18PM -0500, Tom Lane wrote:
David Wheeler <[EMAIL PROTECTED]> writes:
Yes, but even the environment variables get me what I want. I
therefore respectfully submit the attached patch to document them in
the INSTALL file.
It s
Andrew Dunstan wrote:
and a happy April 1 to you too, btw.
;-)
- thomas
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Jim C. Nasby wrote:
On Fri, Mar 31, 2006 at 11:29:15AM -0500, Tom Lane wrote:
This argument falls flat when you consider that the width of a CHAR
entry is measured in characters, not bytes, and therefore its physical
size is not fixed even if its logical width is.
True, but in every case I've
Jim C. Nasby wrote:
> The problem is that PostgreSQL is moving out of the realm of
> "hard-core geeks only" and more into the mainstream.
Someone who has a non-default Perl installation is hardly mainstream.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
--
On Fri, Mar 31, 2006 at 07:01:18PM -0500, Tom Lane wrote:
> David Wheeler <[EMAIL PROTECTED]> writes:
> > Yes, but even the environment variables get me what I want. I
> > therefore respectfully submit the attached patch to document them in
> > the INSTALL file.
>
> It seems rather pointless t
On Fri, Mar 31, 2006 at 11:29:15AM -0500, Tom Lane wrote:
> "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> > About the only reason I use CHAR in other databases systems is when I
> > know that the field will always contain the same amount of data, ie:
> > storing a SHA1. In these cases it's silly to
David Wheeler wrote:
> Yes, but even the environment variables get me what I want. I
> therefore respectfully submit the attached patch to document them in
> the INSTALL file.
Next time you submit a patch, please consider reading it before sending
it out.
--
Peter Eisentraut
http://developer.po
Hi all,
When using intarray operator in a query, postgres dies and restart
itself when executing the following query:
select r1.bet_sentence & r2.bet_sentence
from related r1,related r2
where r1.bet_sentence && r2.bet_sentence
the log file contains the following:
LOG: server process (PID 14
Andrew Dunstan wrote:
We already do use threads on Windows to a limited extent to do things
like timers and pseudo-signal handling.
If this were a greenfields project then your arguments would have
force. But for how long would you like to suspend Postgres development
activity while we r
Thomas Hallgren wrote:
Hi all,
And thanks for very good input regarding a remote alternative to
PL/Java (thread titled "Shared Memory"). I'm convinced that such an
alternative would be a great addition to PL/Java and increase the
number of users. The work to create such a platform that has
"Qingqing Zhou" <[EMAIL PROTECTED]> wrote
>
> "Tom Lane" <[EMAIL PROTECTED]> wrote
>>
>> What we should be seeing, and don't see, is an indication of a backup
>> block attached to this WAL record. Furthermore, I don't see any
>> indication of a backup block attached to *any* of the WAL records in
Hi all,
And thanks for very good input regarding a remote alternative to PL/Java
(thread titled "Shared Memory"). I'm convinced that such an alternative
would be a great addition to PL/Java and increase the number of users.
The work to create such a platform that has the stability and quality o
28 matches
Mail list logo
