Hello again,
A project I am working on has been having problems with pg_dump's output, using 7.3.
Our project's database includes functions that do constraint checking for us, as well
as circular dependencies.
We heard about the changes on the pgsql HEAD/7.5, and have given it a try. It fixed
Michael Meskes <[EMAIL PROTECTED]> writes:
> Hmm, maybe the change is that "-s" is now enabled by default.
Right. I inserted "%option nodefault" into pgc.l (and all our other
flex source files) a day or two ago, after realizing that it is a very
effective tool for catching missed cases in a set o
On Wed, Feb 25, 2004 at 05:22:59PM -0500, Neil Conway wrote:
> /usr/bin/flex -o'pgc.c' pgc.l
> pgc.l:979: warning, -s option given but default rule can be matched
Hmm, maybe the change is that "-s" is now enabled by default. I just
didn't find any mention of this in the docs and no option to enab
Jonathan Scott <[EMAIL PROTECTED]> writes:
> I checked my system, and bison is reporting itself as 1.875. I am using SuSE 9.0,
> and I did have to upgrade to get that configuration message to go away, AND to make
> it compile.
> Could you recommend a way I could get bison to reproduce that mess
Thanks for writing, Tom.
I checked my system, and bison is reporting itself as 1.875. I am using SuSE 9.0, and
I did have to upgrade to get that configuration message to go away, AND to make it
compile.
Could you recommend a way I could get bison to reproduce that message? Perhaps I
should re
At 04:01 PM 26/02/2004, Tom Lane wrote:
there is no basis for assuming that a postmaster failure has
anything to do with problems at the backend levelSo my
opinion is that "kill all the backends when the postmaster
crashes" is a bad idea
Sounds fine. Then a system that will allow a new PM to st
Jonathan Scott <[EMAIL PROTECTED]> writes:
> When using the current head of pgsql, I find four errors when running "make check".
> They are all of the same nature, basically that the expected.out file has "syntax
> error", where as psql is saying "parse error".
What bison version are you using?
Philip Warner <[EMAIL PROTECTED]> writes:
> I'm not event sure I'd go with the rollback; whatever killed the PM may
> make the rest of the system unstable. I'd prefer to see the transactions
> rolled back (if necessary) as part of the log recovery on PM startup, not
> by possibly dying PG proces
Neil Conway <[EMAIL PROTECTED]> writes:
> Tom Lane <[EMAIL PROTECTED]> writes:
>> That's interesting, because I get no such warning here. What version
>> of flex are you using? (Mine is 2.5.4)
> [EMAIL PROTECTED]:/home/nconway]% flex --version
> flex 2.5.31
Oh, that thing. We deliberately back
At 12:19 AM 26/02/2004, Robert Treat wrote:
Yes, roll back any existing/uncommited transactions and shutdown
I'm not event sure I'd go with the rollback; whatever killed the PM may
make the rest of the system unstable. I'd prefer to see the transactions
rolled back (if necessary) as part of the l
I am in Atlanta this week, doing training. I return on Friday, and
have no events scheduled after that.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ c
Tom Lane <[EMAIL PROTECTED]> writes:
> That's interesting, because I get no such warning here. What version
> of flex are you using? (Mine is 2.5.4)
[EMAIL PROTECTED]:/home/nconway]% flex --version
flex 2.5.31
(The flex 2.5.31-22 debian package)
-Neil
---(end of broad
Neil Conway wrote:
> $ cd src/interfaces/ecpg
> $ make
> [ ... ]
> bison -y -d preproc.y
> mv -f y.tab.c ./preproc.c
> mv -f y.tab.h ./preproc.h
> /usr/bin/flex -o'pgc.c' pgc.l
> pgc.l:979: warning, -s option given but default rule can be matched
>
FYI, I am not seeing this with my flex 2.5.4 an
Neil Conway <[EMAIL PROTECTED]> writes:
> /usr/bin/flex -o'pgc.c' pgc.l
> pgc.l:979: warning, -s option given but default rule can be matched
That's interesting, because I get no such warning here. What version
of flex are you using? (Mine is 2.5.4)
regards, tom lane
-
$ cd src/interfaces/ecpg
$ make
[ ... ]
bison -y -d preproc.y
mv -f y.tab.c ./preproc.c
mv -f y.tab.h ./preproc.h
/usr/bin/flex -o'pgc.c' pgc.l
pgc.l:979: warning, -s option given but default rule can be matched
-Neil
---(end of broadcast)---
TIP
On Wed, 2004-02-25 at 03:19, Jonathan M. Gardner wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I'm not sure if my original reply made it through. Ignore the last one if
> it did.
But I liked the last one :-)
>
> On Tuesday 24 February 2004 1:48 pm, Robert Treat wrote:
> > On Tue
On Tuesday 24 February 2004 23:47, Neil Conway wrote:
> Jan Wieck <[EMAIL PROTECTED]> writes:
> > In the case of a postmaster crash, I think something in the system
> > is so wrong that I'd prefer an immediate shutdown.
>
> I agree. Allowing existing backends to commit transactions after the
> post
Jonathan M. Gardner wrote:
You can view my summary at
http://jonathangardner.net/PostgreSQL/materialized_views/matviews.html
Comments and suggestions are definitely welcome.
Fantastic, I was planning on a bit of materialized view investigations
myself
when time permits, I'm pleased to see you've
Dear Shelby Cain ,
Is this expected behavior or perhaps a bug?
For a novice like me can anyone please tell me
1. Will this effect my application developed on PostgreSQL
2. Will my Application break at some point I heavly use the type of
queries defined in the post.
Would be greatfull for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm not sure if my original reply made it through. Ignore the last one if
it did.
On Tuesday 24 February 2004 1:48 pm, Robert Treat wrote:
> On Tue, 2004-02-24 at 12:11, Richard Huxton wrote:
> > On Tuesday 24 February 2004 16:11, Jonathan M. Gardner
20 matches
Mail list logo
