enough initially.
I think you were pretty clear from teh get go, but I simply misunderstood
you.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
#x27;s correct. There shouldn't be much of a performance penalty.
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 2: you can get of
On Wed, Feb 19, 2003 at 12:29:12PM -0500, Tom Lane wrote:
> SQL99. Looks like the parens got lost again by the time of the final
> spec.
I don't think the parens really matter. It's just the different ordering
of columns and values.
Michael
--
Michael Meskes
Email: [EMAI
On Wed, Feb 19, 2003 at 04:37:33PM +0100, Peter Eisentraut wrote:
> That's not what my copy says.
Strange. I just looked at all the docs I have and all have it listed the
way Dave wrote. So I seem to have to update my docs. Peter, could you
send me a copy?
Michael
--
Michael Mesk
ke to
> know right now is which interpretation Informix actually implements.
Informix syntax is listed on
http://www-3.ibm.com/software/data/informix/pubs/library/visionary/infoshelf/sqls/01start.fm.html#156200
It's more than just parens IMO. :-)
Michael
--
Michael Meskes
Email: [EMAIL PROTECTE
are some small issues with it. That's why
they aren't committed yet.
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 3: if posti
s
interested in this feature as you could always keep the numbers as
strings and let the database do all calculation stuff. But then you
cannot use the datatype in C.
And of course I don't like the idea of linking in the GPLed
GNU MP library on default as this would create licensing problems.
Lee.
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
contact me, feel free to use my [EMAIL PROTECTED]
address.
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 1: subscribe and unsubscribe c
gt;
> Yeah, me too. I think the correct fix is '../lib' should become '../ecpglib'
> in ecpg/preproc/Makefile, but am waiting on Michael to confirm.
You're right of course Tom. My first checkin was incomplete. I missed
some files when copying over to my cvs tree.
Micha
s only once and no double work
is required.
Of course the lib should then move out of interfaces, but ecpg could
still call it. Any comments?
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---
ould have an
open API and a backend API calling the same functions.
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
ot;2000-7-12 17:34:29". :-(
Maybe some of you have an idea.
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
ode (preproc.y <=> gram.y) and don't
like the idea of having to do it with a lot more code.
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)-
at I just ran a
short test that worked as advertized. Right now it seems ecpglib does
call the new functions incorrectly. When calling them directly it seems
to work. Unfortunately I have no time to dig into it right now. But I
surely will soon.
Michael
--
Michael Meskes
Email: [EMAIL PROTECT
stamp "Wed Jul 12 17:34:29 2000" becomes "Wed Jul 12
4649:34:26.02 2000" when putting it into timestamp format and back
out. The function is almost identical to timestamp_in resp.
timestamp_out. If these two functions and their helpers are compield
without "-O2" the
ls --without-included-gettext
--enable-__cxa_atexit --enable-clocale=gnu --enable-java-gc=boehm
--enable-objc-gc i386-linux
Thread model: posix
gcc version 3.2.3 20030316 (Debian prerelease)
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use Debian GNU/
the
backend instead of implementing the stuff twice. But I'm still not sure
how high the performance penalty will be.
As for yylineno, it is used in ecpg, yes. Does anyone know how to get
rid of it and still get the correct line number?
Michael
--
Michael Meskes
Email: Michael at Fam-Meske
ed an update but I'm not sure you have the
version that does.
Anyway, if you have and it appears you also have HAVE_LONG_LONG_INT_64
defined, which header file does provide the approprioate constants and
how is it named? It seems INT_MIN etc. are there.
Michael
--
Michael Meskes
Email: Micha
n this for today.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 3: if posting
e a patch.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 8: explain analyze is your friend
.
These are flex/bison internal symbols I'd say. No idea why they are missing
though.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
udes that I didn't need
anymore. It seems this is also not consistant among architectures. Argh!
Sorry.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux!
On Wed, Jul 02, 2003 at 04:20:09PM -0400, Greg Stark wrote:
> bash-2.05b$ flex -V
> flex 2.5.31
I have 2.5.4.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linu
On Fri, Jul 04, 2003 at 03:29:37PM -0400, Tom Lane wrote:
> 2. If so, can I get away with applying this post-feature-freeze? I can
> argue that it's a bug fix, but perhaps some will disagree.
I'd say it is a bug fix.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot D
On Fri, Aug 01, 2003 at 12:06:07PM +0100, Lee Kindness wrote:
> Guys, looking at ecpg from CVS HEAD's 7.4. The following code
> fragement:
> ...
Fix just committed. Should work now.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM: michaelmeskes,
In fact there's another one in common.c with an incorrect #define.
It's fixed now.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---
me system as Oliver to compile.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)--
For now I simply renamed the function. We can look for the reason later.
I'd prefer to get ecpg release ready first. :-)
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debia
in compatlib. No
libpq function is called there directly.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)-
ssl -lm) does fix this?
> Adding the linker options will solve your problems and PostgreSQL will
> work nicely.
Probably in the same manner.
I'm sorry, I didn't see the other mails. They simply got lost in that
virus flood happening these days.
Michael
--
Michael Meskes
Email:
pears that cygwin's "echo" generates a different newline style
> than what got put into sql_features.txt. A possible way to fix this is
> to put the "\." line into sql_features.txt, but maybe there's a cleaner
> answer. Peter, any thoughts?
Putting the "\.&qu
t the consistent ECPG-check
> failures in buildfarm can go away.
Hmm, I thought there was. Joachim, could you comment?
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF
ose .c files they
have around.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(
systems return:
Connection refused (0x274D/10061)
if the connection is refused, or do the numbers differ?
Or in other words, do we need the sed call in pg_regress.sh or could we
do this with a arch specific expected file too?
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Mi
> It shuold be the same - 10061 is the win32 error code. 274D is just the
> hex version of the same one.
Okay, changed this. Please test if you have a MinGW setup.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM
s,
please test and don't be suprised if something break on the buildfarm.
So far it's only tested on my system. It works here. :-)
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMA
a
#define to set a different debug level and the lib sets the regression
flags according to that level. This still needs a global variable in the
library but it is not accessed from the outside.
Hopefully this works on all archs.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Mi
On Fri, Jan 12, 2007 at 01:20:15AM +0100, Joachim Wieland wrote:
> Attached is a patch to get guppy green again (hopefully).
Applied.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EM
2 12:31
postgresql-snapshot/src/interfaces/ecpg/test/expected/compat_informix-dec_test-OpenBSD3.8.broken.stdout
-rw-r--r-- pgsql/pgsql 81524 2007-01-12 12:31
postgresql-snapshot/src/interfaces/ecpg/test/expected/pgtypeslib-num_test2-OpenBSD3.8.broken.stdout
I don't see the difference he
a
> negative value seems very strange to me.
And I see no reason at all why this function is unsigned. After all
there are about 20 different return values. Will change it.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304,
cted
result files for Windows.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end o
investigate.
I did today. This seemed like a strange one, but apparantly a gcc
ABI-bug workaround interfered with the compiler used here because the
workaround wasn't covering all positions.
make check now gives a full list of OKs on Stefan's machine. Thanks for
the account.
Michael
--
On Wed, Jan 31, 2007 at 03:24:24PM -0800, elein wrote:
> Pretty darn vanilla, except for source packages from postgres.
Which Debian version?
I take it you got this message on a full rebuild from clean sources,
right?
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael
On Thu, Jun 22, 2006 at 11:37:08AM -0400, Tom Lane wrote:
> > item #3: Carsten Wolff copyright in informix.c file
> > The file informix.c contains a copyright from Carsten Wolff. Did Carsten
> > directly contribute this file to the PostgreSQL project?
>
> This code was
mitted it.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
-
ve updated your applied patch to just mention the
> author's name, email address, and date.
If that suffices, fine with me.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PRO
On Mon, Jul 31, 2006 at 08:35:00AM -0400, Tom Lane wrote:
> According to the buildfarm, this commit broke the build under
> --enable-thread-safety.
Should be fixed now.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 17914030
Is there any reason why all DROP statements except DROP CAST have two
rules, one with IF_P EXISTS and one without, while DROP CAST uses
opt_if_exists?
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes
bout
what others are seeing soon enough to be able to fix bugs before 8.2.
Just run "make check" in src/interfaces/ecpg and tell us if there is
some test that fails.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AI
Hi,
I just committed some changes by Joachim that should reduce the problems
and the differences by a large margin. Could you please rerun the test
and send us the regression.diff? Thanks a lot in advance.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De
I suspect
> you've got some hard-wired assumption in there that the user hasn't
> specified a nonstandard --port option to configure.
>
> I find it disturbing that the regression test script doesn't mention having
> shut down the temp postmaster, too.
No idea. Joachim?
M
percase 'C'. That should
be fixed now.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)-
eing generated but
> didn't understand it.
Yes, they were expected. But to avoid confusion we just removed this
argument. It's not really needed in terms of regression testing anyway.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net
l/desc: This is strange as the stderr output
seems to be the same. This could be a memory problem too.
- sql/dyntest2 with a different output: Strange again as the log output
seems to be identical.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|N
t; timestamp_defmt_asc(July 14, 1988. Time: 9:15am, %B %d, %Y. Time: %I:%M%p)
> = 1988-07-14 09:15:00, error: 0
> timestamp_defmt_asc(September 6 at 01:30 pm in the year 1983, %B %d at
> %I:%M %p in the year %Y) = 1983-09-06 13:30:00, error: 0
> timestamp_defmt_asc( 1976, Ju
I was thinking about removing this bit of
information from the log if it is a regression test run because it
doesn't bring us more information in terms of regresseion testing.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 1
We changed some things that should remove most of the differences you
had.
Two other diffs looked like you had an older version of ecpglib running. Could
that be?
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo
On Wed, Aug 09, 2006 at 06:39:07PM -0400, Tom Lane wrote:
> I suppose Michael and Joachim are in bed, so I'll try committing this.
> If they don't like it they can fix it in the morning ...
Right we were. :-)
Thanks Tom.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes do
All it does is check for "\r\n" and escape it as one character, i.e.
print "\\\r\n". Please test this is thoroughly as possible. I do not
have a Windows machine to test on, but on my Linux box all
regression tests run successfully no matter which encoding the *.pgc
files hav
ial memory leaks (which I don't worry about
much in short lived frontend apps) they sometimes point to bugs that may
cause real problems.
I just had a small look at one in pg_dump.c. However, it seems the line
numbers are completely different from my CVS snapshot. Are the Coverity
reports you lis
on't think Coverity even knows how long a program may run.
But while I agree that freeing all memory is not needed in a short
running program, I still think we should examine those reports because
they may show some real bugs. At least this is what happened to some
degree in ecpg.
Michael
--
Mic
say it worked for me and it's reaonable to have the paths
shortened IMO.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Li
when the
Fixed.
> 3. unix:postgresql://hostname[:port][/dbname][?options]
Should work too.
> 4. "an SQL string literal containing one of the above forms"
Fixed.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, A
see it now?
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---
d then committed.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(
ated at ago 29 15:16)
> ...
This looks like you're using an old version of the parser. preproc.y was
changed to handle empty database names and the the error you report is
due to an empty db name.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|
uot;results/"
if [ ! -d "$outputdir" ]; then
mkdir -p "$outputdir" || { (exit 2); exit; }
fi
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF
far less friendly environment?
We could modify the backend code to use pgtypeslib, but that would cost
at least a little bit of performance I would guess.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmesk
oth machines. Could you try
running it under gdb to see where it segfaults? I will try to get a hand
on an OpenBSD machine myself, too
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
7;\0'
I think I found this one. Will commit as soon as I finished my tests and
the parser update.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein
the x86 machine doesn't give a
PGTYPES_NUM_UNDERFLOW error when it should. The Sparc correctly throws
that error as do Linux based x86 machines.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jab
an indicator
not correctly set/evaluated. To get more infos I need to get access to
such a machine.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fir
w the question is
what do we do?
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
#include
#include
#include
roc.y didn't trigger a rebuild of preproc.c.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQ
y features at the same time and
divide them into several testcases. This might give us a red from time
to time, but hopefully nothing major.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL
anually too? Or did it stop on its own? I'm
surprised there is no output explaning why it stops.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go
quot; to variable.pgc that should fix this failure.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
--
On Tue, Oct 03, 2006 at 08:26:36PM -0400, Bruce Momjian wrote:
> I have run pgindent for 8.2.
Is there a way to make pgindent skip a directory? It seems it has
changed all expected file in ecpg's regression suite. So we see a lot of
differences now.
Michael
--
Michael Meskes
Email: Mi
ettings of variable the program sets itself.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---
On Wed, Oct 04, 2006 at 04:41:44PM -0400, Bruce Momjian wrote:
> That will prevent it from being changed by pgindent in the future.
Thanks.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jab
t; sizeof (global_threads) / sizeof (global_threads[0]);
++i)
{
if (pthread_create (&global_threads[i], NULL, query_db, NULL))
FATAL ("pthread_create %d failed", i);
}
for (i = 0; i < sizeof (global_threads) / sizeof (global_threads[0]);
++i)
{
if (pthre
you have to find a way
to handle recursion. I would think the best way is to add recursion to
SQL and then completely rewrite the statements.
Also, and that's where it starts to become interesting, how do you plan
to handle negation inside recursion?
Michael
--
Michael Meskes
Email: Michael at
On Wed, Jun 08, 2005 at 10:06:18AM +0530, Abhijit Menon-Sen wrote:
> Are any PostgreSQL hackers planning to be at Linuxtag in Karlsruhe?
Yes and there will be a PostgreSQL booth organized by Peter.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|
On Fri, Apr 30, 2004 at 04:48:33PM -0400, Bruce Momjian wrote:
> Does ecpg need to use the same timezone database as the backend?
I have to check what you changed. ecpg itself does not use the timezone
database, but some of that code is used in pgtypeslib.
Michael
--
Michael Meskes
Em
n it. I just commit patches that I can
personally judge to be good.
But nevertheless I would be very interested in helping with this patch
as recursive query optimization was one are I wokred on for my ph.d.
Granted spare time is a problem, but we should be able to finish this
for 7.6.
Michael
--
On Wed, Jun 30, 2004 at 10:05:35PM -0400, Tom Lane wrote:
> I'm seeing this:
> ...
Sorry, I simply did not see this. Fix just committed.
> Looks like that last patch needs a bit o' work yet ...
As I said it needs some bug fixing. Albeit I expected more severe bugs.
:-)
e it there are no special characters in that COPY, right? The only
difference between the two machines we found was that my was running
under UTF-8.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go R
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
Forgot one question. WHich platform do you use?
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EM
t use ecpg, so I really can't say..)
For ecpg it does not matter which name you use. The typedef is there for
only one reason, namely that Informix uses dtime_t and to be compatible
we have to define that type as well.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 17914
inside
compatlib. Certainly changing the data type there helps building it, but
I wonder what we do if anyone on this particular platform tries to use
Informix compat mode.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECT
se type definitions from our build process. It
should compile now.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
-
simply misread the output?
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
T
's one of the problems. :-)
Why shall 1752 be the default date? The original introduction of
gregorian dates after all was in 1582. And some parts of the earth
didn't switch before the 20th century. So, as pointed out, we'd need a
locale dependant default.
Michael
--
Michael Mesk
eds I have. So, yes, I agree completely
here too.
> Fourth, the registration is run not by the project but by a commercial
> company. That seems inappropriate for all the reasons you can imagine.
And another "me too". I'd say let's remove it unless someone has some
good reason
t it still
doesn't work without the additional entry in sql_features.txt. No idea
why.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
On Mon, Oct 13, 2003 at 02:38:26AM +0100, Oliver Elphick wrote:
> On Sun, 2003-10-12 at 13:27, Michael Meskes wrote:
> > I just tried the latest Debian packages for beta4 and I still cannot
> > initdb. It's the same old problem. Once I add a "\." to sql_features.txt
Does anyone know this bug report:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=204000
We should try to find out if this still errors before releasing 7.4,
don't you think?
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [
.3 and 7.3.2.
>
> I believe the bug probably is the same one reported/fixed here:
Thanks Tom. I will get into contact with the submitter and make sure
he's not having problems with 7.3.3.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michae
ll side effects.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 8: exp
501 - 600 of 652 matches
Mail list logo
