Manfred Spraul wrote:
Bruce Momjian wrote:
if test $enable_debug = yes test $ac_cv_prog_cc_g = yes; then
CFLAGS=$CFLAGS -g
fi
+
+ /* Compile AMD Opteron using gcc in 64-bit mode */
+ if test $GCC = yes; then
+ case $host in
+ ia64-*) CFLAGS=$CFLAGS -m64
+
At 05:24 PM 18/07/2003 +0200, Reinoud van Leeuwen wrote:
Does anyone have a clue what is going wrong? I use Postgresql 7.3.3 on
FreeBSD 4.5.
Is it a before or after trigger. If 'before', are you trying to reference
data that does not exist yet?
Hans-Jürgen Schönig wrote:
Thanks a lot. I will integrate named connections as proposed by the most
recent version of dblink as soon as possible.
Thanks for doing the configure stuff. What we need is Oracle's OCI
interface and libsqlora (http://www.poitschke.de/libsqlora8/).
I was thinking that
One reason I am excited about an Oracle-enabled dblink is that it gives
us a seamless way for PostgreSQL to operate in an evironment with
multiple database products, which I think is important.
As far as the Oracle libraries, once you have an Oracle-enabled patch in
CVS, I will put a some value
Do we have any way of seeing all the predefined psql \set setting?
Right now if you do \set, you see the settings for that client, but you
don't see a list of setting the psql understands, like autocommit. You
can only see those in the psql manual.
On the server side, we have SHOW ALL which
Stuart, were are on this patch? Seems we need GUC additions, though I
can do that for you, and changes to write the head to disk. Was that
completed?
---
Stuart wrote:
Tom Lane wrote:
Stephan Szabo [EMAIL PROTECTED]
Added.
---
Joe Conway wrote:
Bruce Momjian wrote:
I guess we should put array-of-UNKNOWN on the list of things to look at
for 7.5.
Yeah; maybe something like this?
Delay resolution of array expression type as
Bruce Momjian wrote:
I guess we should put array-of-UNKNOWN on the list of things to look at
for 7.5.
Yeah; maybe something like this?
Delay resolution of array expression type as long as possible so that
assignment coercion can be performed on empty array expressions.
Joe
Joe, do you need a TODO added for this?
---
Joe Conway wrote:
Tom Lane wrote:
Joe Conway [EMAIL PROTECTED] writes:
So array[] should produce '{}' of (an array) type determined by the
context? OK -- seems easy
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
On Tue, Jul 15, 2003 at 04:03:13PM -0400, Tom Lane wrote:
Given the current implementation, it seems like there are three possible
behaviors for COMMENT ON DATABASE when the database name isn't the same
as
Hello Jan,
Sunday, July 13, 2003, 1:22:09 PM, you wrote:
JW Joe Conway wrote:
ivan wrote:
ok, but php should build this lang for postgres i think
so, we should talk with php group ?
I have been talking with several people about this on-and-off for a
while now. If I can find some time in
Answer is: a broken flex 2.5.4. There were some commits to NetBSD flex to
use bounded strings. Using 13th July flex source builds a happy PostgreSQL.
Now to track down which bit broke - anyway, not a PostgreSQL problem :-)
could you try usr.bin/lex/initscan.c revision 1.16?
itojun
could you try lex/scan.l 1.13 i just committed?
Yes, that fixed it!
tnx for reporting!
itojun
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Bruce Momjian wrote:
Joe, I can do the configure detection of the Oracle library needed for
/contrib. I don't think we follow the beta freeze as much for /contrib
stuff, but this particular /contrib is more integrated into the main
system than most. If you want to merge it in during the next
Given the current implementation, it seems like there are
three possible
behaviors for COMMENT ON DATABASE when the database name
isn't the same
as the current database:
1. Raise error (what we're doing now). Simple but breaks dump scripts
for the restore-into-different-DB
15 matches
Mail list logo
