Tom Lane writes:
I think the problem is more accurately described thus: Flex generated
files include stdio.h before postgres.h due to the way it lays out the
code in the output. stdio.h does something which prevents switching to
the large file model later on in postgres.h. (This
I've got a couple of free days coming up, so I want to finish domain
support (Check constraints).
Is it safe to teach Var how to deal with values that do not originate
from a tuple? Or should I create a new primnode to deal with these
types of variables.
CREATE DOMAIN dom AS integer
Hi All,
This relates to the recent discussion about floating point output format.
The discussion was at a point where one parameter would be added to
specify the number of extra digits used in fp output formatting.
The parameter would have a 0 default value, a maximum of 2 and the
minimum
Zeugswetter Andreas SB SD [EMAIL PROTECTED] writes:
The issue is, that you need to remove the #include bootstrap_tokens.h
line from the lex file.
Good point; I'm surprised gcc doesn't spit up on that. I've made that
mod and also added the inclusion-order-correction in pqsignal.c.
Rod Taylor [EMAIL PROTECTED] writes:
Is it safe to teach Var how to deal with values that do not originate
from a tuple? Or should I create a new primnode to deal with these
types of variables.
I have no idea what you're talking about, but it sure sounds like
something that should not be in
Pedro M. Ferreira [EMAIL PROTECTED] writes:
int extra_float4_digits, default 0, min -4, max 2
int extra_float8_digits, defualt 0, min -13, max 2
I think a single setting extra_float_digits would be sufficient.
Also, if we concluded that there is a need of 2 more digits, should'nt
this be
Tom Lane wrote:
Pedro M. Ferreira [EMAIL PROTECTED] writes:
int extra_float4_digits, default 0, min -4, max 2
int extra_float8_digits, defualt 0, min -13, max 2
I think a single setting extra_float_digits would be sufficient.
Ok. Assuming,
int extra_float_digits, default 0, min -13, max 2
Pedro M. Ferreira [EMAIL PROTECTED] writes:
Tom Lane wrote:
I think a single setting extra_float_digits would be sufficient.
Ok. Assuming,
int extra_float_digits, default 0, min -13, max 2
If extra_float_digits==-13 and we are outputing a float4 this results in
a negative value for
Tom Lane wrote:
Pedro M. Ferreira [EMAIL PROTECTED] writes:
If extra_float_digits==-13 and we are outputing a float4 this results in
a negative value for FLT_DIG+extra_float_digits.
You would want to clamp the values passed to %g to not less than 1.
I'd favor code like
int ndig = FLT_DIG +
Pedro M. Ferreira [EMAIL PROTECTED] writes:
I am attaching the diff's made with diff -u. Sources were from Debian
source package Version 7.2.1-2woody2.
Looks good, will keep to apply after we branch for 7.4 development.
BTW, did you check to see if this affects the geometric types or not?
I
Tom Lane wrote:
Looks good, will keep to apply after we branch for 7.4 development.
BTW, did you check to see if this affects the geometric types or not?
I am not sure that they go through float8out; they may need similar
adjustments in their output routines.
Only checked arrays.
I will check
Morning all ...
As I was unable to figure out a way of merging HEAD into a BRANCH
(BRANCH into HEAD is easy), I moved the REL7_3_STABLE tag up to today, so
that the BRANCH is in a more appropriate location.
I've packaged up beta4 based on the branch, and its currently up
and
Tom Lane wrote:
BTW, did you check to see if this affects the geometric types or not?
I am not sure that they go through float8out; they may need similar
adjustments in their output routines.
In fact they need adjustments.
The *_out routines (in src/backend/utils/adt/geo_ops.c) for the
Pedro M. Ferreira [EMAIL PROTECTED] writes:
These functions produce output with (for pair_encode):
sprintf(str, %.*g,%.*g, digits8, x, digits8, y);
digits8 is defined as ,
#define P_MAXDIG DBL_DIG
static int digits8 = P_MAXDIG;
I think it would be done the same way as for float4_out
Tom Lane wrote:
Yeah. In fact I'd be inclined to remove the static variable and make
the code match float8out exactly (do DBL_DIG + extra_float_digits).
P_MAXDIG is only used in the lines below:
#define P_MAXDIG DBL_DIG
#define P_MAXLEN (2*(P_MAXDIG+7)+1)
static int digits8 = P_MAXDIG;
Marc G. Fournier [EMAIL PROTECTED] writes:
As I was unable to figure out a way of merging HEAD into a BRANCH
(BRANCH into HEAD is easy), I moved the REL7_3_STABLE tag up to today, so
that the BRANCH is in a more appropriate location.
It looks like this was only 99.44% right. There are
Pedro M. Ferreira [EMAIL PROTECTED] writes:
Is it ok to remove #define P_MAXDIG DBL_DIG,
change P_MAXLEN to 2*(DBL_DIG+7)+1) and
remove the line 'static int digits8 = P_MAXDIG;' ?
Perhaps P_MAXLEN now needs to be (2*(DBL_DIG+2+7)+1), considering
that we'll allow extra_float_digits to be
Tom Lane wrote:
Pedro M. Ferreira [EMAIL PROTECTED] writes:
Is it ok to remove #define P_MAXDIG DBL_DIG,
change P_MAXLEN to 2*(DBL_DIG+7)+1) and
remove the line 'static int digits8 = P_MAXDIG;' ?
Perhaps P_MAXLEN now needs to be (2*(DBL_DIG+2+7)+1), considering
that we'll allow
Peter Eisentraut [EMAIL PROTECTED] writes:
Why do we have two doc builds anyway?
Mainly because Bruce is willing to expend the cycles to rebuild his
nearly on-demand. Last I checked, the build on hub is only updated
once or twice a day, so it's not as useful for verifying doc checkins.
Peter Eisentraut [EMAIL PROTECTED] writes:
Jason Tishler writes:
1. If ipc-daemon is not running, then cygipc's shmget() will return
EACCES.
2. This causes PostgreSQL's InternalIpcMemoryCreate() to return
NULL.
3. This causes PostgreSQL's PGSharedMemoryCreate() to spin looking
for
On Fri, Nov 01, 2002 at 10:22:42AM -0500, Tom Lane wrote:
I've committed fixes for the other issues too, so CVS tip should now
pass cleanly on your platform.
I've built the snapshot from CVS tip and now the regression tests pass
with both GCC 2.95.1 and Compaq C V6.4-216 (dtk) on
Digital UNIX
Hi,
I just discovered, that there is missing a const when passing a buffer to
PQescapeBytea and PQunescapeBytea. I fixed it and tried to create a usable
diff (I'm not so familar to diff).
Tommi
*** postgresql-7.3b3/src/interfaces/libpq/fe-exec.c 2002-09-04 22:31:47.0 +0200
---
Hello,
I used TPCC to test postgreSQL 7.3 beta3 version.
My test steps are showed as follow,
1st, the number of TPCC simulation processes is 100,
run time is 7200 seconds. The consistency test was
got through successfully.
2nd, the number of TPCC simulation processes is
On Mon, 4 Nov 2002, Tom Lane wrote:
Marc G. Fournier [EMAIL PROTECTED] writes:
As I was unable to figure out a way of merging HEAD into a BRANCH
(BRANCH into HEAD is easy), I moved the REL7_3_STABLE tag up to today, so
that the BRANCH is in a more appropriate location.
It looks like
Marc G. Fournier [EMAIL PROTECTED] writes:
Perhaps easiest to just re-delete them in the branch? Or is there a
cleaner way?
Easiest is to re-delete them ...
Okay, done that. REL7_3_STABLE branch now matches CVS tip --- or did
until I branded HEAD's configure.in as 7.4devel, a few moments
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.
I'm aware of the following problems that need a
On Mon, Nov 04, 2002 at 08:10:29PM -0500, Mike Mascari wrote:
Actually, I was thinking along the lines of a true CREATE
DATABASE LINK implementation, where multiple databases could
participate in a distributed transaction. That would require the
backend in which the main query is
On Mon, 2002-11-04 at 09:44, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
Is it safe to teach Var how to deal with values that do not originate
from a tuple? Or should I create a new primnode to deal with these
types of variables.
I have no idea what you're talking about, but it
Perhaps P_MAXLEN now needs to be (2*(DBL_DIG+2+7)+1), considering
that we'll allow extra_float_digits to be up to 2. What's it used for?
Yes. I guess so, because it is used in what I think is a memory
allocation function. P_MAXLEN is only used twice:
Curse my slowness, but what's the
I'm now implementing 2PC replication and distributed transaction. My 2PC
needs some supports in startup packet to establish a replication session
or a recovery session.
BTW, my 2PC replication is working, and I'm implementing 2PC recovery now.
I would like to here more about your
Darren Johnson [EMAIL PROTECTED] wrote:
I would like to here more about your implementation. Do you have some
documentation that I
could read?
Documentation is not available, but I have some slides for my presentation.
http://snaga.org/pgsql/20021018_2pc.pdf
Some answers for your
Hi Oleg Teodor,
This behaviour is causing problems in my search engine:
australia=# select 'banana/pineapple'::mquery_txt;
mquery_txt
'banana/pineapple'
(1 row)
In our case the forward slash symbol should really be treated as a word
break. Are there any cases where
one too many things removed? this build worked earlier today, so its only
since removing those directories that something has broken ...
openjade -D . -D ./ref -c /usr/local/share/sgml/docbook/dsssl/modular/catalog -
d stylesheet.dsl -i output-html -t sgml postgres.sgml
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
Curse my slowness, but what's the actual problem being fixed here?
Two things:
* allow pg_dump to accurately dump and restore float quantities (setting
float_extra_digits to 2 during the dump will accomplish this, at least
on systems with
On Mon, 2002-11-04 at 23:10, Marc G. Fournier wrote:
one too many things removed? this build worked earlier today, so its only
since removing those directories that something has broken ...
Bruce left an extra /entry tag at on line 1534 of installation.sgml :)
Can't make a patch because
Marc G. Fournier [EMAIL PROTECTED] writes:
one too many things removed?
Just broken SGML markup ... fixed I think ...
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
I don't see why 2PC would require any protocol-level change. I would
think that the API would be something like
BEGIN;
issue some commands ...
PRECOMMIT;
-- if the above does not return an error, then
COMMIT;
In other words, 2PC would require some new
Questions have arisen during discussions about errors relating
to how to support error codes without changing the FE/BE
protocols. (see TODO.detail/error)
Now that the protocol is up for revision, how about supporting
sql state strings, error codes, and other information directly in
the protocol.
Grant Finnemore [EMAIL PROTECTED] writes:
Now that the protocol is up for revision, how about supporting
sql state strings, error codes, and other information directly in
the protocol.
Ah, thanks for pointing that out. Error codes would be another thing
we can ideally support in 7.4, and we'd
Tom Lane wrote:
I don't see why 2PC would require any protocol-level change. I would
think that the API would be something like
BEGIN;
issue some commands ...
PRECOMMIT;
-- if the above does not return an error, then
COMMIT;
In other words, 2PC would
On Mon, 4 Nov 2002, Bruce Momjian wrote:
Sure, script attached. It uses a few of my other scripts so it will
need customization. I can easily supply those missing scripts too.
I run it every 7 minutes from cron with:
*/7 * * * * root /letc/pgsgml /dev/null 21
I can even
Ports list updated:
http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-platforms.html
---
Sean Chittenden wrote:
Or at least it's *trying* to apply it for 4.7 --- as near as I
can tell without testing, the
On Mon, 2002-11-04 at 21:40, Marc G. Fournier wrote:
On Mon, 4 Nov 2002, Bruce Momjian wrote:
Sure, script attached. It uses a few of my other scripts so it will
need customization. I can easily supply those missing scripts too.
I run it every 7 minutes from cron with:
*/7 * *
Hi all,
Who's an Admin for the PostgreSQL IRC Channel (#postgresql) on
irc.openprojects.net?
The topic there is advertising some items for some guy on eBay, claiming
it supports the PostgreSQL channel, and no-one knows anything about it.
There also doesn't appear to be any IRC Admin's about.
Tom,
Peter,
On Mon, Nov 04, 2002 at 02:43:01PM -0500, Tom Lane wrote:
Peter Eisentraut [EMAIL PROTECTED] writes:
To me, this is a bug in PostgreSQL.
I disagree: just because cygipc returns error codes chosen at random
doesn't mean that we should neglect the clear meaning of an error
code.
Peter,
On Wed, Oct 30, 2002 at 07:36:40PM +0100, Peter Eisentraut wrote:
Dave Page writes:
Hackers: As the Cygwin release that is actively supported is the
binary distribution that Jason builds, I would think this is OK to
be listed as supported if no-one disagrees...
I disagree. We
On Tue, 2002-10-29 at 17:56, Greg Patnude wrote:
Does anyone know of a reasonable means of synchronizing two (or more)
postgreSQL database servers in order to maintain two COMPLETE concurrent
copies of the same database ?
I'm not sure how complete it is (just starting to look at this myself)
On Wed, Oct 30, 2002 at 10:59:39PM -0500, Tom Lane wrote:
What's the basis for your assertion that it's planning things that
don't need it? Given a JOIN-constrained query I do not believe the
planner will look at any cases other than the intended join order.
Well, that was a loose choice of
On Mon, 4 Nov 2002, Tom Lane wrote:
Peter Eisentraut [EMAIL PROTECTED] writes:
Why do we have two doc builds anyway?
Mainly because Bruce is willing to expend the cycles to rebuild his
nearly on-demand. Last I checked, the build on hub is only updated
once or twice a day, so it's not as
What is the status of the tgenabled field in pg_trigger? It would be so
nice to be able to disable just a single trigger on a table rather than
having to disable all triggers. The docs say not presently checked
everywhere it should be, so disabling a trigger by setting this false
does not work
Marc G. Fournier [EMAIL PROTECTED] writes:
Mainly because Bruce is willing to expend the cycles to rebuild his
nearly on-demand. Last I checked, the build on hub is only updated
once or twice a day, so it's not as useful for verifying doc checkins.
'k, is there a reason why it can't be run
Laurette Cisneros [EMAIL PROTECTED] writes:
What is the status of the tgenabled field in pg_trigger? It would be so
nice to be able to disable just a single trigger on a table rather than
having to disable all triggers. The docs say not presently checked
everywhere it should be, so disabling
Sure, script attached. It uses a few of my other scripts so it will
need customization. I can easily supply those missing scripts too.
I run it every 7 minutes from cron with:
*/7 * * * * root /letc/pgsgml /dev/null 21
I can even install the whole thing on postgresql.org if you
On Mon, 2002-11-04 at 15:52, Tom Lane wrote:
Marc G. Fournier [EMAIL PROTECTED] writes:
Perhaps easiest to just re-delete them in the branch? Or is there a
cleaner way?
Easiest is to re-delete them ...
Okay, done that. REL7_3_STABLE branch now matches CVS tip --- or did
until I
Does this resolve our AIX compile problem?
---
Tom Lane wrote:
Zeugswetter Andreas SB SD [EMAIL PROTECTED] writes:
The issue is, that you need to remove the #include bootstrap_tokens.h
line from the lex file.
Good
Ports list updated:
http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-platforms.html
---
Alessio Bragadini wrote:
On Fri, Nov 01, 2002 at 10:22:42AM -0500, Tom Lane wrote:
I've committed fixes for the other
This has been saved for the 7.4 release:
http:/momjian.postgresql.org/cgi-bin/pgpatches2
---
Tommi Maekitalo wrote:
Hi,
I just discovered, that there is missing a const when passing a buffer to
PQescapeBytea
Jason Tishler writes:
1. If ipc-daemon is not running, then cygipc's shmget() will return
EACCES.
2. This causes PostgreSQL's InternalIpcMemoryCreate() to return
NULL.
3. This causes PostgreSQL's PGSharedMemoryCreate() to spin looking
for accessible shared
Bruce Momjian writes:
Yeah. I don't use your docs build anymore unless I really have to...
the one at hub.org is much more responsive.
Oh, that is a problem. Thanks.
Why do we have two doc builds anyway?
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of
Neil Conway wrote:
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.
snip
If I've missed
Mike Mascari [EMAIL PROTECTED] writes:
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?
My understanding is that 2PC is one way to
Neil Conway wrote:
Mike Mascari [EMAIL PROTECTED] writes:
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?
My understanding is that 2PC is
Hi,
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 replication and
Or at least it's *trying* to apply it for 4.7 --- as near as I
can tell without testing, the above scrap of resultmap code is
wrong because both of the i.86 lines will match on FreeBSD 4.7,
and I think the pg_regress coding will take the last match.
Larry, did you actually test the
Justin Clift [EMAIL PROTECTED] writes:
Hi all,
Who's an Admin for the PostgreSQL IRC Channel (#postgresql) on
irc.openprojects.net?
The only person I've seen with ops is someone called 'raja', who is
only rarely (i.e. once every couple months) in the channel. I talked
to lilo about getting
As I was unable to figure out a way of merging HEAD into a BRANCH
(BRANCH into HEAD is easy), I moved the REL7_3_STABLE tag up to today, so
that the BRANCH is in a more appropriate location.
It is easy to move both directions; I've done it. You need to have the
right stuff in your checked-out
Out of curiousity, is there an easy (heh) way to upgrade(change?) a
checked out tree to be off the branch?
cvs update -rYOUR_BRANCH_NAME_HERE .
- Thomas
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to
Hi Neil,
Cool. It's fixed now. We've just recreated the channel and started
giving operator access to the right people.
:-)
Regards and best wishes,
Justin Clift
Neil Conway wrote:
Justin Clift [EMAIL PROTECTED] writes:
Hi all,
Who's an Admin for the PostgreSQL IRC Channel
68 matches
Mail list logo
