I have not researched any deeper,but currently it fails with
[EMAIL PROTECTED] postgresql-8.0.3]$
CC=/opt/ibmcmp/vac/7.0/bin/xlc ./configure
..A..
checking for int timezone... yes
checking types of arguments for accept()... configure: error:
could not determine argument types
The odds
On P, 2005-05-29 at 11:26 -0400, Tom Lane wrote:
Hannu Krosing [EMAIL PROTECTED] writes:
I have not researched any deeper,but currently it fails with
checking types of arguments for accept()... configure: error: could not
determine argument types
So look at config.log and see what's
Bruce Momjian wrote:
I was suggesting ESCAPE 'string' or ESC 'string'. The marker has to
be before the string so scan.l can alter its processing of the string
--- after the string is too late --- there is no way to undo any
escaping that has happened, and it might already be used by gram.y.
On E, 2005-05-30 at 12:21 +0300, Hannu Krosing wrote:
On P, 2005-05-29 at 11:26 -0400, Tom Lane wrote:
Hannu Krosing [EMAIL PROTECTED] writes:
I have not researched any deeper,but currently it fails with
checking types of arguments for accept()... configure: error: could not
Hannu Krosing wrote:
it needs this:
extern int accept (int __fd, __SOCKADDR_ARG __addr,
socklen_t *__restrict __addr_len);
how does one add yet another set of arguments for accept() to
configure ?
One patches the file config/ac_func_accept_argtypes.m4. Presumably, you
On 2005-05-30, Neil Conway [EMAIL PROTECTED] wrote:
On Wed, 2005-03-23 at 10:04 -0500, Tom Lane wrote:
I think last night's discussion makes it crystal-clear why I felt that
this hasn't been sufficiently thought through. Please revert until the
discussion comes to a conclusion.
Are there
There has been discussion in the past of including number of days as
part of the Interval structure in addition to the current months and
time components. Here are some mailing list threads where the topic
has arisen.
[Re: [GENERAL] '1 year' = '360 days' ](http://
Christopher Kings-Lynne wrote:
I think we can tell people in 8.1 that they should modify their
applications to only use '', and that \' might be a security problem in
the future. If we get to that then using ESC or not only affects input
of values and literal backslashes being entered,
I read the PHP addslashes() manual page:
http://us3.php.net/addslashes
First, I see what people mean about PHP having most of the complex
content in comments, rather than in the actual manual text, and this
tendency is certainly something we want to avoid --- you end up having
to digest
Christopher Kings-Lynne wrote:
I read the PHP addslashes() manual page:
http://us3.php.net/addslashes
First, I see what people mean about PHP having most of the complex
content in comments, rather than in the actual manual text, and this
tendency is certainly something we want
Peter Eisentraut wrote:
Bruce Momjian wrote:
I was suggesting ESCAPE 'string' or ESC 'string'. The marker has to
be before the string so scan.l can alter its processing of the string
--- after the string is too late --- there is no way to undo any
escaping that has happened, and it might
Bruce Momjian pgman@candle.pha.pa.us writes:
Christopher Kings-Lynne wrote:
Each comment is supposed to be acted upon (ie. fixed in source), then
deleted.
Right, they are more _usage_ comments, but still I think they could be
consolidated into manual text.
If that's supposed to
Michael Glaesemann [EMAIL PROTECTED] writes:
When the string is read by DecodeInterval, the days component is
assigned to tm_mday. It seems relatively straightforward to use this
input to provide the interval-day value. However, I'm wondering what
range of days this the interval-day
Michael,
One advantage of this is that it would allow '1 day' to have a
different meaning that '24 hours', which would be meaningful when
crossing daylight saving time changes. For example, PostgreSQL
returns the following results:
I've been stumping for this for years. See my arguments
Josh Berkus josh@agliodbs.com writes:
Unfortunately, it appears that tri-partitioning INTERVAL ( year/month ;
week/day ; hour/minute/second ) is a violation of the SQL spec which has only
the two partitions ( year/month ; week/day/hour/minute/second ).
I think it's an extension of the spec,
FYI, two weeks ago I attended the Computer Communications Industry
Association (http://www.ccianet.org/) 2005 Summit in Washington. I was
invited as a member of an open source project.
It was a great opportunity for our project to get visibility in
Washington among industry lobbyist and
In 8.0, PostgreSQL lost its previously postulated ability to be
cross-compiled and it turns out some people actually used that, so
here's an attempt to fix it.
The problem is that the program zic in src/timezone/ is built and run
during the build process, which doesn't work if it's compiled by
Does anyone object if we moved to Autoconf 2.59? It's been the last
release for 18 months now, so it seems reasonable to settle on it. I'm
not actually looking to use features from there, but it gets a bit
annoying to have to keep so many Autoconf versions around.
--
Peter Eisentraut
What about our threading configure test? That doesn't allow cross
compilation either, does it?
---
Peter Eisentraut wrote:
In 8.0, PostgreSQL lost its previously postulated ability to be
cross-compiled and it turns out
Peter Eisentraut [EMAIL PROTECTED] writes:
The problem is that the program zic in src/timezone/ is built and run
during the build process, which doesn't work if it's compiled by a
cross-compiler.
Why don't we instead arrange to run it during install?
I'm not real thrilled with the notion of
Peter Eisentraut [EMAIL PROTECTED] writes:
Does anyone object if we moved to Autoconf 2.59? It's been the last
release for 18 months now, so it seems reasonable to settle on it. I'm
not actually looking to use features from there, but it gets a bit
annoying to have to keep so many
Bruce Momjian wrote:
Peter Eisentraut wrote:
Bruce Momjian wrote:
I was suggesting ESCAPE 'string' or ESC 'string'. The marker has to
be before the string so scan.l can alter its processing of the string
--- after the string is too late --- there is no way to undo any
escaping that
Tom Lane wrote:
Bruce Momjian pgman@candle.pha.pa.us writes:
Here is a new version of the three \x hex support patches. I have added
\x for psql variables, which is the last patch.
I have IM'ed with Peter and he is now OK with the idea of supporting \x,
with the underestanding that it
Added to TODO:
* Prevent child tables from altering constraints like CHECK that were
inherited from the parent table
---
Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
Doing anything to
Mark Kirkwood wrote:
I couldn't use int4 as the underlying datatype is unsigned int (not
available as exposed Pg type). However, using int8 sounds promising (is
int8 larger than unsigned int on 64-bit platforms?).
Blocknumber is defined as uint32 in block.h - so should always be safe
to
Mark Kirkwood wrote:
Mark Kirkwood wrote:
I couldn't use int4 as the underlying datatype is unsigned int (not
available as exposed Pg type). However, using int8 sounds promising
(is int8 larger than unsigned int on 64-bit platforms?).
Blocknumber is defined as uint32 in block.h - so
On Fri, May 27, 2005 at 11:12:06AM -0400, Tom Lane wrote:
Heikki Linnakangas [EMAIL PROTECTED] writes:
Looking at the sequence, at least the relcache init file stuff looks if
not broken at least a bit heavy-handed...
I was planning to change that ;-) ... using separate 2PC action records
Well, it'll still be necessary to keep 2.53 around, unless you want to
move to 2.59 for future releases of the back branches too ... which
might be OK, I'm not sure.
I thought it was to help the public not have to keep so many versions
around :)
Chris
---(end of
I'm not sure whether this article has been mentioned here before,
but it definitely is worth a read:
http://www.usenix.org/events/fast03/tech/full_papers/anderson/anderson_html/
From the proceedings of the FAST '03 conference:
More than an interface - SCSI vs. ATA
Dave Anderson,
Bruce Momjian pgman@candle.pha.pa.us writes:
The goal, at some point, is that we would have two types of strings, ''
strings and E'' strings. '' strings don't have any special backslash
handling for compatibility with with the ANSI spec and all other
databases except MySQL (and in MySQL it
Greg Stark wrote:
Bruce Momjian pgman@candle.pha.pa.us writes:
The goal, at some point, is that we would have two types of strings, ''
strings and E'' strings. '' strings don't have any special backslash
handling for compatibility with with the ANSI spec and all other
databases except
Yea, it is a great paper. It is an HTML version of the SCSI PDF I
mentioned a few weeks ago:
http://www.seagate.com/content/docs/pdf/whitepaper/D2c_More_than_Interface_ATA_vs_SCSI_042003.pdf
Someone had mentioned it on the lists a few months ago but I only read
it recently and
Tom,
This is a story that is evolving. Anyone else use StorageReview? Great
comprehensive drive benchmarks:
http://www.storagereview.com/
Check the comparisons between 15K RPM SCSI drives and the 2004 Western
Digital 10K RPM SATA (Raptor) drives. The Raptors are an interesting hybrid
of
Luke Lonergan wrote:
Tom,
This is a story that is evolving. Anyone else use StorageReview? Great
comprehensive drive benchmarks:
http://www.storagereview.com/
Check the comparisons between 15K RPM SCSI drives and the 2004 Western
Digital 10K RPM SATA (Raptor) drives. The Raptors are an
Mark Kirkwood wrote:
Luke Lonergan wrote:
Although the benchmark numbers are pretty good, they have only published
(what looks like) results for sequential IO. It would be interesting to
see the random ones, as this would tell us how effective the TCQ
implementation is.
Referring to
Greg Stark [EMAIL PROTECTED] writes:
The only thing I'm not clear on is what exactly is the use case for E''
strings. That is, who do you expect to actually use them?
The case that convinced me we need to keep some sort of backslash
capability is this: suppose you want to put a string including
36 matches
Mail list logo
