Peter Eisentraut wrote:
> Bruce Momjian wrote:
> > I have updated the release notes for 7.4.1 and HISTORY as of Dec 14.
> > I will make further adjustments before the 7.4.1 release.
>
> Would you care to put back the correct upgrade instructions that I had
> written there?
There where? I don't
Alvaro Herrera wrote:
> On Tue, Dec 16, 2003 at 11:17:11AM -0800, David Fetter wrote:
>
> [Moved to hackers -- this belongs to -docs anyway, doesn't it?]
>
> > With all due respect, Peter, it is only implicit in the docs, and that
> > is not always good enough. An explicit example will help, as
Michael Meskes wrote:
> On Tue, Dec 16, 2003 at 02:01:51PM -0500, Bruce Momjian wrote:
> > Maybe that fixes the Red Hat issue, but we have the Cygwin issue with
> > Win32's sqltypes.h, and there is the issue for other platforms, no? Is
> > that install change going to be for all platforms?
>
> T
Neil Conway said:
> Andrew Dunstan <[EMAIL PROTECTED]> writes:
>> In normal operation the only thing that should be signalling a
>> backend is the postmaster.
>
> Oh? What about LISTEN/NOTIFY?
>
er, yeah. *self-lart*
+" ... or another backend"
cheers
andrew
---(end o
Neil Conway kirjutas K, 17.12.2003 kell 00:37:
> Andrew Dunstan <[EMAIL PROTECTED]> writes:
> > In normal operation the only thing that should be signalling a
> > backend is the postmaster.
>
> Oh? What about LISTEN/NOTIFY?
IIRC cancelling queries is done by making a connection to a new backend
a
On Tue, Dec 16, 2003 at 10:29:20PM +, Jaime Casanova wrote:
> >On Fri, Dec 12, 2003 at 09:59:23AM +0530, Somasekhar Bangalore wrote:
> >>I too had the same problem; There was one query which used to take a
> >>very long time. What I did was, I took a backup of the whole database.
> >>Reinstal
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> In normal operation the only thing that should be signalling a
> backend is the postmaster.
Oh? What about LISTEN/NOTIFY?
-Neil
---(end of broadcast)---
TIP 9: the planner will ignore your desire to cho
On Fri, Dec 12, 2003 at 09:59:23AM +0530, Somasekhar Bangalore wrote:
> Hi,
>
> I too had the same problem; There was one query which used to take a
> very long time. What I did was, I took a backup of the whole database.
> Reinstalled postgres on a different mount point and restored the data
> b
On Tue, 16 Dec 2003, scott.marlowe wrote:
> > > If you want to prevent "accidential" access, start postmaster on a
> > > non-standard port.
> >
> > That seems like an unfriendly thing to do. You'd have to check to see what
> > port is "standard" for this particular installation, and pick someth
On Tue, 16 Dec 2003, Jon Jensen wrote:
> On Tue, 16 Dec 2003, Jan Wieck wrote:
>
> > If you want to prevent "accidential" access, start postmaster on a
> > non-standard port.
>
> That seems like an unfriendly thing to do. You'd have to check to see what
> port is "standard" for this particular
Magnus Hagander wrote:
Absolutely, but there are other signals to send, no? Or you might want
to send a signal directly to a backend (to cancel for example), as you
can do on Unix.
In normal operation the only thing that should be signalling a backend
is the postmaster.
cheers
andrew
--
On Tue, 16 Dec 2003, Jan Wieck wrote:
> If you want to prevent "accidential" access, start postmaster on a
> non-standard port.
That seems like an unfriendly thing to do. You'd have to check to see what
port is "standard" for this particular installation, and pick something
else. You may choos
On Tue, 16 Dec 2003, Alvaro Herrera wrote:
> BTW, what happened to the $QUOTE$ quoting idea? Was it applied, or
> even developed?
I believe it's still on the to-do list, but was pushed off until 7.5 or
whenever it gets done.
Jon
---(end of broadcast)
On Tue, Dec 16, 2003 at 11:17:11AM -0800, David Fetter wrote:
[Moved to hackers -- this belongs to -docs anyway, doesn't it?]
> With all due respect, Peter, it is only implicit in the docs, and that
> is not always good enough. An explicit example will help, as
> PostgreSQL's quoting system woul
Tom Lane wrote:
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
Then again, in the case of pg_upgrade, wouldn't just disabling access from
anywhere except localhost prevent others from getting in?
Not if your normal operating mode includes connections from clients
running locally. I really don't s
> -Original Message-
> From: Magnus Hagander [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 16, 2003 7:53 AM
> To: Andrew Dunstan; PostgreSQL-development; pgsql-hackers-win32
> Subject: Re: [pgsql-hackers-win32] [HACKERS] [PATCHES] fork/exec patch
>
>
> > > If you need a response on
On Tue, Dec 16, 2003 at 02:01:51PM -0500, Bruce Momjian wrote:
> Maybe that fixes the Red Hat issue, but we have the Cygwin issue with
> Win32's sqltypes.h, and there is the issue for other platforms, no? Is
> that install change going to be for all platforms?
The problem as I see it is that som
Tom Lane wrote:
> Michael Meskes <[EMAIL PROTECTED]> writes:
> > Well, it is not really an ecpg file, but one needed for compatibility.
> > And, yes, Peter is correct, this file may be included directly by some
> > apps.
>
> I was under the impression that this issue had already been resolved
> am
> > If you need a response once it has actually run, then the
> main thread
> > needs to do signal polling now and then. This has the bad
> sideeffect
> > that the main thread will block completely until the signal is
> > delivered, which might be a while.
> >
> > I don't know what the semant
Bruce Momjian wrote:
> I have updated the release notes for 7.4.1 and HISTORY as of Dec 14.
> I will make further adjustments before the 7.4.1 release.
Please fix the SGML syntax errors.
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmast
Magnus Hagander wrote:
Bruce Momjian wrote:
Have you looked at the CONNX signal code on the Win32 page:
http://momjian.postgresql.org/main/writings/pgsql/win32.html
It uses shared memory and events.
Yes, and I just did again. I guess I must be missing
something, though -
I don't see what
Bruce Momjian wrote:
> I have updated the release notes for 7.4.1 and HISTORY as of Dec 14.
> I will make further adjustments before the 7.4.1 release.
Would you care to put back the correct upgrade instructions that I had
written there?
---(end of broadcast)---
Michael Meskes <[EMAIL PROTECTED]> writes:
> Well, it is not really an ecpg file, but one needed for compatibility.
> And, yes, Peter is correct, this file may be included directly by some
> apps.
I was under the impression that this issue had already been resolved
among you, Lamar, and the Red Ha
On Tue, Dec 16, 2003 at 10:38:00AM -, Dave Page wrote:
> > But the file has to be called sqltypes.h or it won't work.
>
> Why, is it used directly by user code? (I never used ecpg)
Well, it is not really an ecpg file, but one needed for compatibility.
And, yes, Peter is correct, this file may
Dann Corbit kirjutas T, 16.12.2003 kell 12:40:
> I suspect if you do "explain" against the SQL of the view, the answer
> will be apparent.
>
> Donning my "Karnak the magnificent hat {borrowed from Johnny Carson}":
> You are missing an index.
>
> For the best help, post the SQL of your view, and
On Tuesday 16 December 2003 10:32, Claudia D'amato wrote:
> I have a quite complicated view with roughly 1 record. When I execute a
> simple query like this
> "select * from myview"
> postgres respond after 50 - 55 minutes roughly. I hope that someone can
> help me with some suggestion ab
Hi, I am developing a program using postgres and linux like operating
system. My problem is this:
I have a quite complicated view with roughly 1 record. When I
execute a simple query like this
"select * from myview"
postgres respond after 50 - 55 minutes roughly. I hope that someone
c
Title: Message
I
suspect if you do "explain" against the SQL of the view, the answer will be
apparent.
Donning my "Karnak the magnificent hat {borrowed from Johnny Carson}":
You are missing an index.
For
the best help, post the SQL of your view, and also the Schema definition for the
ta
> -Original Message-
> From: Peter Eisentraut [mailto:[EMAIL PROTECTED]
> Sent: 16 December 2003 09:09
> To: Dave Page
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: Re: [HACKERS] 7.4 include file conflict
>
> Dave Page writes:
> > We could prefix the names
Title: Postgres respond after toomany times to a query view
Hi, I am developing a program using postgres and linux like operating system. My problem is this:
I have a quite complicated view with roughly 1 record. When I execute a simple query like this
"select * from myview"
post
Title: Postgres respond after toomany times to a query view
Hi, I am developing a program using postgres and linux like operating system. My problem is this:
I have a quite complicated view with roughly 1 record. When I execute a simple query like this
"select * from myview"
po
> Bruce Momjian wrote:
>
> >Have you looked at the CONNX signal code on the Win32 page:
> >
> > http://momjian.postgresql.org/main/writings/pgsql/win32.html
> >
> >It uses shared memory and events.
> >
> >
> >
>
> Yes, and I just did again. I guess I must be missing
> something, though -
Hi,
> Alternative thought: just recommend that if possible, people
> take a filesystem dump of their old PGDATA directory after
> stopping the old postmaster. This would be sufficient for
> retreating to the prior version if needed. It might or might
> not be slower than copying all the file
Dave Page writes:
> We could prefix the names as Ray suggested , or move them
> into a pg subdirectory and change the includes to .
But the file has to be called sqltypes.h or it won't work.
---(end of broadcast)---
TIP 7: don't forget to increas
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]
> Sent: 16 December 2003 01:17
> To: Ray Aspeitia
> Cc: [EMAIL PROTECTED]
> Subject: Re: [HACKERS] 7.4 include file conflict
>
>
> Where are we going on the pgsql/include file conflicts?
> sqltypes.h is very common
35 matches
Mail list logo
