Awhile back I wrote:
>> As long as you only do this in check_function_bodies mode it seems
>> safe enough. One possible problem (if it's done towards the end of
>> parsing as you've suggested for dead-code checking) is that a syntax
>> error in a SQL statement might confuse the plpgsql parser into
It appears to be just that.
Great, It works!
*** ./expected/polymorphism.out Wed Dec 1 20:00:56 2004
--- ./results/polymorphism.out Tue Dec 21 19:06:12 2004
***
*** 349,532
select f3, myaggp01a(*) from t group by f3;
f3 | myaggp01a
+---
c | {}
a | {}
Looking at the two patches I just applied I think it might fix your
problem. The problem was actually the general problem of pg_ctl -w start
not returning a non-zero.
---
Steve McWilliams wrote:
> Hello,
>
> I tried sending
[EMAIL PROTECTED] writes:
> The regression test fails on 'polymorphism' on three different computers with
> various architectures.
Define "fails" (regression diffs output would be nice).
> Besides the configure options stated below, BLCKSZ was redefined from 8192 to
> 16384 before running configu
Hi,
The regression test fails on 'polymorphism' on three different computers with
various architectures.
(I hope this point was not raised before, but I did not find any relevant mail
about it with '[BUGS]'in the subject line and 'polymorphism' in message body)
Besides the configure options st
Hello,
I tried sending this the other week but for some reason it hasn't gone
through, so I am resending:
I am using Postgresql-8.0.0beta4 on Windows XP Pro and have noticed that
attempts to run pg_ctl as a service fail when the "-w" option is included.
So if I register the service as follows:
I have noticed on linux that if you try to start postmaster via "pg_ctl
-w", but the postmaster fails to run (e.g. if you forgot to create
PGDATA), it returns a 0 exit code. It needs to return a non-0 exit code
if postmaster failed to start, when you are using the "-w" option to wait
for it to sta
The following bug has been logged online:
Bug reference: 1352
Logged by: Steve Schafer
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0 Beta
Operating system: Windows 2000 Pro, sp 4, up to date
Description:100's of postgres.exe tasks created
Details:
I
Tony Caduto wrote:
Well, I got my 8.0 RC1 working the same as my 7.4.5 and it is for sure
because of some difference in the SQL engine.
On my 7.4.5 box I had the following in the postgresql.conf file:
enable_seqscan = true (this is the default setting)
7.4.5 had no problems using the indexes wit
unsubscribe [EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
10 matches
Mail list logo
