Tatsuo Ishii wrote:
It seems to be resonable to leave #define UNICODE_CONVERSION somewhere
(maybe in pg_config.h).
That's what I was after.
--
Hannu
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
Tatsuo Ishii writes:
Why are you so worrying about finding syslog() in configure? We have
already done lots of function testings. Is there anything special with
syslog()?
All the other functions we test for come with a replacement plan. Either
we choose between several similar alternatives
On Fri, Sep 07, 2001 at 04:05:58PM -0400, Bruce Momjian wrote:
...
OK, I have modified the CVS CREDS code to work on FreeBSD and BSD/OS,
and hopefully NetBSD. I talked to Jason at Linuxworld and I think this
code should work. Please test the CVS version and let me know. OpenBSD
doesn't
Thomas Lockhart writes:
Keep in mind that he is a mathematician, and I'll guess that he won't
have much patience with folks who expect a result for a factorial of a
fractional number ;)
Real mathematicians will be perfectly happy with a factorial for a
fractional number, as long as it's
Tatsuo Ishii writes:
Why are you so worrying about finding syslog() in configure? We have
already done lots of function testings. Is there anything special with
syslog()?
All the other functions we test for come with a replacement plan. Either
we choose between several similar
Hi all,
Attached is a patch that adds support for specifying a location for
indexes via the create database command.
I believe this patch is complete, but it is my first .
This patch allows index locations to be specified as different from data
locations. Is this a feature direction we
On Fri, Sep 07, 2001 at 04:05:58PM -0400, Bruce Momjian wrote:
...
OK, I have modified the CVS CREDS code to work on FreeBSD and BSD/OS,
and hopefully NetBSD. I talked to Jason at Linuxworld and I think this
code should work. Please test the CVS version and let me know. OpenBSD
On Wed, Sep 12, 2001 at 02:45:10PM +0200, Peter Eisentraut wrote:
Thomas Lockhart writes:
Keep in mind that he is a mathematician, and I'll guess that he won't
have much patience with folks who expect a result for a factorial of a
fractional number ;)
Real mathematicians will be
Ciao,
I had the need to exclude tables from the dump so I made this patch,
I do something like
pg_dump -X \Test_*\ -X \Devel*\ test
I'm not a C guru, but it work, the only thing I was unable to get rid
of is the dump of sequences for that table,
so I have to add -X tablename_id_seq
If you
What is it? 8) is it middleware? Is it pre-built applications? I'm confused!
-r
At 11:34 PM 9/12/01 -0500, Haroldo Stenger wrote:
Hi dear people,
(My condolences to all afected by terrorist acts in US)
As I have been telling for a while, GeneXus database rapid application
developing tool,
Mikheev, Vadim [EMAIL PROTECTED] writes:
The more general and standard way to go are TABLESPACEs.
But probably proposed feature will be compatible with
tablespaces, when we'll got them:
Will it be? I'm afraid of creating a backwards-compatibility
problem for ourselves when it comes
...
At the very least I'd like to see some information demonstrating
how much benefit there is to this proposed patch, before we
consider whether to adopt it. If there's a significant performance
benefit to splitting a PG database along the table-vs-index divide,
then it's interesting as a
...
At the very least I'd like to see some information demonstrating
how much benefit there is to this proposed patch, before we
consider whether to adopt it. If there's a significant performance
benefit to splitting a PG database along the table-vs-index divide,
then it's interesting
The more general and standard way to go are TABLESPACEs.
But probably proposed feature will be compatible with
tablespaces, when we'll got them:
Will it be? I'm afraid of creating a backwards-compatibility
problem for ourselves when it comes time to implement tablespaces.
As I said,
just change the work tablespace below to location and that is exactly
what this patch is trying to do. You can think of the LOCATION and
INDEX_LOCATION provided to the create database command as the default
storage locations for these objects. In the future, I want to enable
the DBA to specify
I agree that groups of objects in separate data storage areas are needed
and that is what I am trying to get to. Don't you think that Postgresql
with locations/files is the same as Oracle tablespaces. I don't think
we want to invent our own filesystem (which is what a tablespace really
is...).
Vadim,
I don't understand the WAL issue below, can you explain. The dir name
is the same name as the database with _index added to it. This is how
the current datpath stuff works. I really just copied the datpath code
to get this patch to work...
Also I have been running this patch (both
I don't understand the WAL issue below, can you explain. The dir name
is the same name as the database with _index added to it. This is how
the current datpath stuff works. I really just copied the datpath
code to get this patch to work...
At the time of after crash recovery WAL is not able
Also I have been running this patch (both 7.1.3 and 7.2devel) against
some of my companies applications. I have loaded a small database 10G
We are not familiar with your applications. It would be better to see
results of test suit available to the community. pgbench is first to
come in mind.
I could also symlink all index files back to the tblnode directory?
I don't understand the WAL issue below, can you explain. The dir
name
is the same name as the database with _index added to it. This is
how
the current datpath stuff works. I really just copied the datpath
code to get
Giuseppe Tanzilli - CSF writes:
Ciao,
I had the need to exclude tables from the dump so I made this patch,
I do something like
pg_dump -X \Test_*\ -X \Devel*\ test
We already have an option -t to select the table name to dump. This could
be expanded to interpret the name as a pattern of
Moving the test to a system with SCSI disks gave different results.
There is NO difference between having the indexes on the same disk or
different disk with the data while running pgbench. So I leave it up to
you guys as to include the patch or not. I do believe that even if
performance
Moving the test to a system with SCSI disks gave different results.
There is NO difference between having the indexes on the same disk or
different disk with the data while running pgbench. So I leave it up to
you guys as to include the patch or not. I do believe that even if
performance
Attached is a patch that adds support for specifying a location for
indexes via the create database command.
This patch allows index locations to be specified as different from data
locations. Is this a feature direction we want to go in? Comments?
I have not looked at the patch, either
I am very new to this mailinglist so I apologize if I start talking early but
I've been working as a sysadmin and that kind of problems for a long while
now and my suggestion is that it is a start but I think that we should aim a
little higher than this and use something more like the Oracle
Attached is a patch that adds support for specifying a
location for indexes via the create database command.
I believe this patch is complete, but it is my first .
This patch allows index locations to be specified as
different from data locations. Is this a feature direction
we
On Wed, Sep 12, 2001 at 02:45:10PM +0200, Peter Eisentraut wrote:
Thomas Lockhart writes:
Keep in mind that he is a mathematician, and I'll guess that he won't
have much patience with folks who expect a result for a factorial of a
fractional number ;)
Real mathematicians will
New problems with CVSup. We should all upgrade asap, though I'm not sure
of the current status of builds for non-FreeBSD machines. Marc, could we
possibly install this on the postgresql.org machine(s)?
- Thomas
-Original Message-
From: [EMAIL PROTECTED]
28 matches
Mail list logo
