James Rogers kirjutas T, 07.10.2003 kell 01:48:
Hi,
I guess what I am wondering
is whether there is any kind of quasi-official mechanism for putting
certain features in certain future versions depending on the nature and
significance of implementing those features and the number of things
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm trying to compile PostgreSQL 7.4 beta4 on Irix 6.5.5, o200, r1
(IP27) with MIPSPro compilers version 6.5.
I've read FAQ_IRIX and saw these lines:
PostgreSQL 7.2 has been run on MIPS r8000, r1(both ip25 and ip27)
and r12000(ip35)
Devrim GUNDUZ writes:
/usr/freeware/bin/gcc -O2 -Wall -Wmissing-prototypes
- -Wmissing-declarations -I../../src/include -U_NO_XOPEN4 -c -o isinf.o
isinf.c
In file included from ../../src/include/c.h:60,
from isinf.c:3:
On Fri, Oct 03, 2003 at 09:17:16AM -0700, Joshua D. Drake wrote:
What if the feature does break compatibility with old features?
What if it is truly a new feature?
There is _no_ mechanism in the community right now for testing all
these new features in the so-called stable tree.
I have
Gaetano Mendola writes:
Some corrections.
I don't understand why your patch changes è to e' and à to a'. Also,
please make your next patch so that it can be applied to the file it.po
(not psql.pot).
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of
Peter Eisentraut wrote:
Gaetano Mendola writes:
Some corrections.
I don't understand why your patch changes è to e' and à to a'. Also,
please make your next patch so that it can be applied to the file it.po
(not psql.pot).
Because with some terminal the character è, à, and other characters
Gaetano Mendola wrote:
Peter Eisentraut wrote:
Gaetano Mendola writes:
Some corrections.
I don't understand why your patch changes è to e' and à to a'. Also,
please make your next patch so that it can be applied to the file it.po
(not psql.pot).
Because with some terminal the character è,
I grabbed the patched BSD indent from a mirror. Here's a couple of points:
. with a little trial and error GNU indent 2.2.9 actually did quite a
reasonable job for me last night. But I guess YMMV. I'm curious to know
what nasty mangling it does.
. the file is a compressed tar file - it would be
Andreas Pflug wrote:
Gaetano Mendola wrote:
Peter Eisentraut wrote:
Gaetano Mendola writes:
Some corrections.
I don't understand why your patch changes è to e' and à to a'. Also,
please make your next patch so that it can be applied to the file it.po
(not psql.pot).
Because with some
Gaetano Mendola wrote:
Right, anyway there was typos in the translation, and my vi was unable
to display: è, à. Anyway is a common stuff and well accepted have a'
instead of à.
Hi Gaetano,
in the era of unicode I don't quite see why this needs to be
acceptable... I wouldn't accept it.
It
Andreas Pflug wrote:
Gaetano Mendola wrote:
Right, anyway there was typos in the translation, and my vi was unable
to display: è, à. Anyway is a common stuff and well accepted have a'
instead of à.
Hi Gaetano,
in the era of unicode I don't quite see why this needs to be
acceptable... I
Andrew Sullivan wrote:
On Fri, Oct 03, 2003 at 09:17:16AM -0700, Joshua D. Drake wrote:
What if the feature does break compatibility with old features?
What if it is truly a new feature?
There is _no_ mechanism in the community right now for testing all
these new features in the
Andrew Dunstan wrote:
I grabbed the patched BSD indent from a mirror. Here's a couple of points:
. with a little trial and error GNU indent 2.2.9 actually did quite a
reasonable job for me last night. But I guess YMMV. I'm curious to know
what nasty mangling it does.
GNU indent does a
Bruce Momjian wrote:
Andrew Sullivan wrote:
On Fri, Oct 03, 2003 at 09:17:16AM -0700, Joshua D. Drake wrote:
What if the feature does break compatibility with old features?
What if it is truly a new feature?
There is _no_ mechanism in the community right now for testing all
these
Andrew Dunstan wrote:
Agreed. Great Bridge was going to test our releases and only distribute
the good ones --- obviously they were thinking of Linux kernels and not
PostgreSQL. You almost need a commercial company to do testing with
Linux kernels. PostgreSQL doesn't require this, and I
Bruce Momjian writes:
I think we should change the check_function_bodies to something more
general. I like restore_validation_mode because it could also be used
to disable foreign key checks which we are discussing. An even more
general idea would be to have something like restore_mode, and
Peter Eisentraut wrote:
Bruce Momjian writes:
I think we should change the check_function_bodies to something more
general. I like restore_validation_mode because it could also be used
to disable foreign key checks which we are discussing. An even more
general idea would be to have
Hello,
I believe that the Int8/BigInt items are known issues but I have a
knew programmer that ran into it
over the weekend (he didn't call me when he encountered the problem,
when he should of) and we have a
customer that burned some significant time on it as well. Will this be
fixed in 7.4?
Bruce Momjian wrote:
Andrew Dunstan wrote:
I grabbed the patched BSD indent from a mirror. Here's a couple of points:
. with a little trial and error GNU indent 2.2.9 actually did quite a
reasonable job for me last night. But I guess YMMV. I'm curious to know
what nasty mangling it does.
BTW, there's a bug in entab.c, too. This line:
#include ../include/c.h
should read
#include ../../include/c.h
cheers
andrew
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister
Andrew Dunstan wrote:
BTW, there's a bug in entab.c, too. This line:
#include ../include/c.h
should read
#include ../../include/c.h
Thanks. Fixed.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your
Hello,
O.k. so everyone is basically in agreement of no new features to be
backported.
How do we implement a stable release maintainer for back releases? I assume
we set a scope of of what would go in security/bug fixes only?
Sincerely,
Joshua Drake
--
Command Prompt, Inc., home of Mammoth
Joshua D. Drake wrote:
But the kernel goes through this reliable/unreliable cycle --- they
would be better off just making the old kernel more and more reliable
and focusing on the new kernel for features.
The reliable/unreliable cycle will kill your user base.
The popularity of
But the kernel goes through this reliable/unreliable cycle --- they
would be better off just making the old kernel more and more reliable
and focusing on the new kernel for features.
The reliable/unreliable cycle will kill your user base.
The popularity of Linux would argue that statement a
Hi,
This is for relational database theory experts on one hand and
imlementers of real-world alications on the other hand. If there was
a chance to start again and design SQL afresh, for best
cleaness/power/performance what changes would you make? What would
_your_ query language (and the
I was just contemplating how to make postgres parallel (for DSS
applications)... Has anyone done work on this? It looks to me like there
are a couple of obvious places to add parallel operation:
Stage 1) I/O , perhaps through MPIO - would improve tablescanning and
load/unload operations. One
Hi,
I have been studying the basic limitation that the number of committed
transactions per second possible in a relational databases. Since
each transaction requires at least write-ahead log data to be flushed
to disk the upper bound of transactions per second is equal to the
number of
Hi Christopher,
Just to go through your points.
COMMIT NOSYNC; -- (sacrifice durability of non-critical transaction
for overall speed). So, the question is what people, especially those
who have done DBMS work, think about this!
I think that whenever my organization cares THAT much about
Hi, all.
Hi, developers !
PostgreSQL is growing
Applications are growing older and larger too.
Don't we need some printing tools?
I feel I need a tool to print relation and unheritance diagrams from sources
on SQL.
My sources are too large to drawing diagrams manually now.
I believe it is
[EMAIL PROTECTED] (Tom Lane) wrote in message news:[EMAIL PROTECTED]...
Christopher Browne [EMAIL PROTECTED] writes:
In the last exciting episode, [EMAIL PROTECTED] (Seun Osewa) wrote:
So I want to ask, what if databases have a 'COMMIT NOSYNC;' option?
Another possibility in this would be
Hi
I have developed a new buffer policy for biological databases, I want
to implement it on postgresql.So I will have to buffer manager of
pgsql.How should I do it?
Which files I will have to change what type of changes I will have
to make. Is there any document which describes code of buffer
Joshua D. Drake wrote:
eh.. i could see some things, like tsearch2 or pg_autovacuum, which
afaik are almost if not completely compatible with 7.3, which will not
get back ported. Also fixes in some of the extra tools like psql could
be very doable, I know I had a custom psql for 7.2 that back
Looking for candidates who have experience in developing database/OS kernel
using C/C++/Java
This is for position(s) in south bay area, CA.
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
Marc G. Fournier wrote:
On Sat, 27 Sep 2003, Bruce Momjian wrote:
I have been thinking it might be time to start allowing external
programs to be called when certain events occur that require
administrative attention --- this would be a good case for that.
Administrators could configure shell
Christopher Browne [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]...
I think an implementor would be better off using an SQL database
underneath, and using their code layer in between to accomplish the
divorce from the aspects of SQL that they disapprove of.
That is, in fact, the
Seun Osewa wrote:
Sometimes I wonder why its so important to model data in the rela-
tional way, to think of data in form of sets of tuples rather than
tables or lists or whatever. I mean, though its elegant and based
on mathematical principles I would like to know why its the _right_
Hi,
Many of the regression tests are failing on my OSX 10.2.6 machine. I have
put the regression.diffs file here
http://bugs.sghms.ac.uk/downloads/regression.diffs
Has this been seen before?
Thanks
adam
Check her over and let me know if there are any problems ... will do a
full general
On 3 Oct 2003 21:39:03 GMT, Christopher Browne [EMAIL PROTECTED]
wrote:
There are two notable 'projects' out there:
1. There's Darwen and Date's Tutorial D language, defined as part
of their Third Manifesto about relational databases.
2. newSQL http://newsql.sourceforge.net/, where
In article [EMAIL PROTECTED], Seun Osewa
[EMAIL PROTECTED] writes
Thanks for the links.
Christopher Browne [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]
125932.news.uni-berlin.de...
There are two notable 'projects' out there:
1. There's Darwen and Date's Tutorial D language,
In article [EMAIL PROTECTED], Lee Fesperman
[EMAIL PROTECTED] writes
If you don't care for mathematical principles, there's always ad-hoc database
models.
Check out Pick, OO and XML databases. They're interested in what works and
ignore
elegance and mathematical principles.
Mathematical
Anthony W. Youngman [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]...
In article [EMAIL PROTECTED], Lee Fesperman
[EMAIL PROTECTED] writes
If you don't care for mathematical principles, there's always ad-hoc database
models.
Check out Pick, OO and XML databases. They're
Thanks for the links.
Christopher Browne [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]...
There are two notable 'projects' out there:
1. There's Darwen and Date's Tutorial D language, defined as part
of their Third Manifesto about relational databases.
2. newSQL
Steve Yalovitser wrote:
Hello,
I'd like to know if its possible to coopt the postgres storage subsystem to
rely entirely on ram based structures, rather than disk. Any documentation
or ideas would be appreciated.
Cheers,
Steve
---(end of
On Fri, 03 Oct 2003 11:53:05 -0400 Tom Lane [EMAIL PROTECTED] wrote:
Rainer Klute [EMAIL PROTECTED] writes:
[ some good comments, but a few things I want to respond to ]
+ CREATE SCHEMA: Sometimes a schema created in PostgreSQL
disappears if there is nothing in it.
This is more
Dear PostgreSQL masters,
I know this might like a childish question and you
probably might have a good laugh over this but I
would like to learn how PostgreSQL works inside-out.
Could anyone please give me some pointers of where to start
in/from the sourcecode?
I am grateful for any help.
[EMAIL PROTECTED] (monu agrawal) wrote:
Hi
I have developed a new buffer policy for biological databases, I want
to implement it on postgresql.So I will have to buffer manager of
pgsql.How should I do it?
Which files I will have to change what type of changes I will have
to make.
Very
Folks,
Pardon me if this has already been discussed and rejected for good reason.
Now that we have Statement-level triggers, is there any reason we shouldn't
have triggers on SELECT? Such triggers could be extremely useful for
databases with tight security audit requirements.
--
-Josh
On Fri, Oct 03, 2003 at 03:00:36PM +0100, Patrick Welche wrote:
On Fri, Oct 03, 2003 at 12:59:19PM +0200, Michael Meskes wrote:
On Mon, Sep 29, 2003 at 06:41:48PM +0100, Patrick Welche wrote:
Today's cvs doesn't compile. I think it is due to
cvs diff -r1.7 -r1.8
-Original Message-
From: Seun Osewa [mailto:[EMAIL PROTECTED]
Sent: Friday, October 03, 2003 11:52 AM
To: [EMAIL PROTECTED]
Subject: [HACKERS] Dreaming About Redesigning SQL
Hi,
This is for relational database theory experts on one hand
and imlementers of real-world
On Sun, 5 Oct 2003, Bruce Momjian wrote:
Neil Conway wrote:
On Sun, 2003-10-05 at 17:45, Bruce Momjian wrote:
Neil Conway wrote:
Depending on what part of the source you're interested in, a book on
DBMS implementation might also be useful, such as
Wow, $100.
Well, it's a
Martin Rusoff wrote:
I was just contemplating how to make postgres parallel (for DSS
applications)... Has anyone done work on this? It looks to me like there
are a couple of obvious places to add parallel operation:
Stage 1) I/O , perhaps through MPIO - would improve tablescanning and
I have lately been taking the position that Linux is only a
second-best choice for production use, precisely because of the
constant introduction of shiny new features in the supposed stable
branch.
That's what all us FreeBSD users learnt a long time ago :P
Chris
Should we add a variable that is set from the dump filew that identifies
the version of PostgreSQL that generated the dump?
SET dumped_version = 7.3
With something like that, does it have to be reissued after every
\connect in the dump?
Chris
---(end of
On Tue, 2003-10-07 at 21:31, Christopher Kings-Lynne wrote:
Should we add a variable that is set from the dump filew that identifies
the version of PostgreSQL that generated the dump?
SET dumped_version = 7.3
With something like that, does it have to be reissued after every
Hi,
i notice that when HeapTuple data are populated by a trigger
then the table oid can be retrieved from HeapTuple-t_tableOid.
When HeapTuple is populated by
SPI_exec(select * from foobar when id=667);
tuple = SPI_tuptable-tvals[0] (id is PK and row with 667 exists)
then tuple-t_tableOid is
On Fri, 3 Oct 2003, Tom Lane wrote:
I think in 7.4 there may be an optimization that skips the tuple
projection step in this particular case, but if you can in fact see
t_tableOid in 7.4, it'd be an implementation artifact rather than
something we will promise to support in future. The
Bruce Momjian [EMAIL PROTECTED] writes:
Should we add a variable that is set from the dump filew that identifies
the version of PostgreSQL that generated the dump?
SET dumped_version = 7.3
Is that identifying the backend version, or the pg_dump version?
Without a solid rationale for
Joshua D. Drake [EMAIL PROTECTED] writes:
Will this be fixed in 7.4?
No.
regards, tom lane
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Should we add a variable that is set from the dump filew that identifies
the version of PostgreSQL that generated the dump?
SET dumped_version = 7.3
Is that identifying the backend version, or the pg_dump version?
Without a
Josh Berkus [EMAIL PROTECTED] writes:
Now that we have Statement-level triggers, is there any reason we shouldn't
have triggers on SELECT?
Plenty, although I'm too tired to recall 'em all. The fundamental
problem with this is that it turns SELECT into an operation with
side-effects.
Hi
the problem is to avoid users from viewing functions code (in general db
structures) when connecting to db by means of pgpadmin client.
My db contains several tables and functions and I need to make users viewing
only a restricted
number of tables. It works for tables, as it's possible to
61 matches
Mail list logo
