Arjen van der Meijden <[EMAIL PROTECTED]> writes:
> I found another example, in case you're interested:
Did you apply the patch?
regards, tom lane
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignor
Hi Senenca,
I think that I do not need readline, so I will try to recompile
--without-readline.
The server is running AIX 5.1 ML 2. Before I recompile I will apply ML 7,
thought I already did it.
As this is an old F40 I cannot upgrade to AIX 5.2 or above, so I have to stay
on 5.1.
I think ther
The following bug has been logged online:
Bug reference: 2090
Logged by: Andreas Schmidt
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.0
Operating system: Linux
Description:error in man-page of postmaster
Details:
'man postmaster' describes the -h option
Tom Lane wrote:
Arjen van der Meijden <[EMAIL PROTECTED]> writes:
I found another example, in case you're interested:
Did you apply the patch?
No, it was just another test-case I stumbled upon. And I'd rather nog
install development versions of postgresql on the machine in question.
If you
On Fri, Dec 02, 2005 at 12:30:17AM -0500, Tom Lane wrote:
> "Dick Snippe" <[EMAIL PROTECTED]> writes:
> > setting umask 077 makes sense for the data files, but not per se for the
> > logfile.
>
> The logfile typically contains data just as sensitive as the data files,
true.
> so I disagree.
we
Hi Tom,
I found another example, in case you're interested:
This query:
SELECT * FROM meuktracker m
JOIN pwproduktrel p ON tabel = 'm' AND tabelid = m.id
WHERE m.id = (select min(id) from meuktracker where id > 7810);
It works ok if the subquery is replaced by the actual result, but this
on
David J N Begley <[EMAIL PROTECTED]> writes:
> Earlier today, Tom Lane wrote:
>> Please provide a concrete test case, not handwaving.
> C:\Program Files\PostgreSQL\8.1\bin>createdb concrete "Test Case"
> CREATE DATABASE
> COMMENT
> C:\Program Files\PostgreSQL\8.1\bin>psql -q concrete
> concrete=#
Tom Lane wrote:
> Given that -C overlaps pg_dumpall functionality anyway, maybe it should
> dump GRANT/REVOKE commands for the database too? Any thoughts pro or
> con out there?
I agree. Why have only half a funcionality if we can have the whole
thing? Maybe we can take that part of of pg_dump
Dick Snippe wrote:
> On Fri, Dec 02, 2005 at 12:30:17AM -0500, Tom Lane wrote:
>
> > "Dick Snippe" <[EMAIL PROTECTED]> writes:
> > > setting umask 077 makes sense for the data files, but not per se for the
> > > logfile.
> >
> > The logfile typically contains data just as sensitive as the data fi
I fail to see how this is a bug, but...
[EMAIL PROTECTED]:46]~:9%psql -tc 'show port' ;
5432
On Thu, Dec 01, 2005 at 09:32:46PM +, Manoj Kumar wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2086
> Logged by: Manoj Kumar
> Email address: [EMAIL PR
>From http://www.postgresql.org/docs/8.1/interactive/triggers.html:
The trigger function must be defined before the trigger itself can be
created. The trigger function must be declared as a function taking no
arguments and returning type trigger. (The trigger function receives its
input through a s
On Fri, Dec 02, 2005 at 12:59:17PM -0500, Bruce Momjian wrote:
> Dick Snippe wrote:
> > On Fri, Dec 02, 2005 at 12:30:17AM -0500, Tom Lane wrote:
> >
> > > "Dick Snippe" <[EMAIL PROTECTED]> writes:
> > > > setting umask 077 makes sense for the data files, but not per se for the
> > > > logfile.
>
"Andreas Schmidt" <[EMAIL PROTECTED]> writes:
> 'man postmaster' describes the -h option wrong:
> instead of "... The value can also be a space-separated list of
> addresses..." you have to write "The value can also be a comma-separated
> list of addresses...".
Fixed, thanks. (That was correct
13 matches
Mail list logo
