On May 6, 2005, at 11:57 AM, Tom Lane wrote:
bash-3.00$ /usr/bin/pg_dump.broken planet
bash-3.00$
Does it work if you direct the output into a file, instead of
letting it
come to your terminal (which seems a bit useless anyway)?
Interesting.
Redirecting it worked, but I'm pretty sure at one poin
Jeff - <[EMAIL PROTECTED]> writes:
> When I run pg_dump w/these settings the following happens running
> pg_dump (.broken is hte original file from the rpm)
> bash-3.00$ /usr/bin/pg_dump.broken planet
> bash-3.00$
Does it work if you direct the output into a file, instead of letting it
come to
On Fri, May 06, 2005 at 11:21:26AM -0400, Bruce Momjian wrote:
> Peter Eisentraut wrote:
> > Am Freitag, 6. Mai 2005 16:55 schrieb Bruce Momjian:
> > > A blurb about what? No one else has reported such a problem so we have
> > > no reason to assume it isn't a misconfiguration on your end.
> >
> >
On May 6, 2005, at 11:23 AM, Tom Lane wrote:
Jeff - <[EMAIL PROTECTED]> writes:
Eventually we found it was SELinux was preventing pg_dump from
producing output.
That's a new one on me. Why was it doing that --- mislabeling on
the pg_dump executable, or what?
We've got a stock CentOS 4 install
I na
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Fri, 6 May 2005, Tom Lane wrote:
Jeff - <[EMAIL PROTECTED]> writes:
Eventually we found it was SELinux was preventing pg_dump from
producing output.
That's a new one on me. Why was it doing that --- mislabeling on
the pg_dump executable, or what
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Am Freitag, 6. Mai 2005 16:55 schrieb Bruce Momjian:
>> A blurb about what? No one else has reported such a problem so we have
>> no reason to assume it isn't a misconfiguration on your end.
> *Countless* people are constantly reporting problems that
Jeff - <[EMAIL PROTECTED]> writes:
> Eventually we found it was SELinux was preventing pg_dump from
> producing output.
That's a new one on me. Why was it doing that --- mislabeling on
the pg_dump executable, or what?
regards, tom lane
---(end o
Peter Eisentraut wrote:
> Am Freitag, 6. Mai 2005 16:55 schrieb Bruce Momjian:
> > A blurb about what? No one else has reported such a problem so we have
> > no reason to assume it isn't a misconfiguration on your end.
>
> *Countless* people are constantly reporting problems that can be attribute
Am Freitag, 6. Mai 2005 16:55 schrieb Bruce Momjian:
> A blurb about what? No one else has reported such a problem so we have
> no reason to assume it isn't a misconfiguration on your end.
*Countless* people are constantly reporting problems that can be attributed to
selinux. We really need to
Jeff - wrote:
> I think we should put some notes about SELinux causing issues with
> pgsql in the OS notes or FAQ.
>
> Myself and a few coworkers just spent a few hours tracking down why
> pg_dump would produce no output. We'd fire it up in strace and we'd
> see all the successful write cal
I think we should put some notes about SELinux causing issues with
pgsql in the OS notes or FAQ.
Myself and a few coworkers just spent a few hours tracking down why
pg_dump would produce no output. We'd fire it up in strace and we'd
see all the successful write calls, but not output.
We co
11 matches
Mail list logo
