On Sat, 23 Oct 2004, Tom Lane wrote:
> Josh Berkus <[EMAIL PROTECTED]> writes:
> > Dennis and I are hashing this out on IRC. The second option would be to
> > simply put SET SESSION AUTHORIZATION statements before each and every
> > statement in the pg_dump. This would make each statement "a
[late on a Saturday night, getting ready to go to bed, after putting four to
bed: this topic is just too good to pass onapologies in advance...]
On Saturday 23 October 2004 17:16, Steve Crawford wrote:
> > Its also an unusual replication scheme in that, more often than
> > not, the slaves con
I am seeing regression test failures on HPUX 11.23 (on ia64) using gcc
3.4.1. The failures occur because refint.so fails to load:
/usr/lib/hpux32/dld.so: Unsatisfied code symbol '__divdi3' in load module
'/house/tgl/pgsql/src/test/regress/../../../contrib/spi/refint.so'.
ERROR: could not load l
Tom,
> No, you misunderstood me. The bug of which you are complaining (namely,
> ALTER OWNER not fixing the ACL list) is gone in 8.0; therefore you are
> arguing from a faulty premise about whether this change is needed.
Aha, I misunderstood the terse phrasing ;-)
Will have to try destruction t
Josh Berkus <[EMAIL PROTECTED]> writes:
> Dennis and I are hashing this out on IRC. The second option would be to
> simply put SET SESSION AUTHORIZATION statements before each and every
> statement in the pg_dump. This would make each statement "atomic" as far as
> user ownership is concerned
unsubscribe-digest
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
Tom,
> The main objection to this is that it makes the dump completely
> unportable.
That's a powerful argument.
Dennis and I are hashing this out on IRC. The second option would be to
simply put SET SESSION AUTHORIZATION statements before each and every
statement in the pg_dump. This w
Josh Berkus <[EMAIL PROTECTED]> writes:
> Instead, we should have a "CREATE WITH OWNER username" extension to all
> of our CREATE statements.
The main objection to this is that it makes the dump completely
unportable.
> CREATE followed by ALTER ... CHANGE OWNER would not be an adequate sub
People:
Having today spent 3.5 hours correcting a pg_dump file with permissions
problems, I've come to the inescapable realization that the "SESSION
AUTHORIZATION" concept is WAY too fragile.
Instead, we should have a "CREATE WITH OWNER username" extension to all
of our CREATE statements
Hello,
i have installed postgres 8.0 beta3 as a program on
my pc on windows xp. I have read on the installation note file that postgres
server will not run with administrative permissions. I have read on your forum
that this happened because i have installed the beta version: is it true t
The Slony-I team is proud to present the 1.0.4 release of the most
advanced replication solution for the most advanced Open Source
Database in the world.
The release tarball is available for download
http://developer.postgresql.org/~wieck/slony1/download/slony1-1.0.4.tar.gz
There are a limite
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> SELECT to_number('485-', '999S');
> to_number
> ---
>485
> Is this a bug or intentional?
Tracing through this, it looks like the problem is that NUM_processor()
has no switch case for NUM_S (nor does the default case raise an error,
> Its also an unusual replication scheme in that, more often than
> not, the slaves control the masters.
As the slave of a replica with an 86 day 16 hour uptime I've also
discovered that the new I/O functions take some adjustment as does
working around the lack of sleep(3).
Cheers,
Steve
-
This is from one of the examples in the documentation:
SELECT to_char(-485, '999S');
to_char
-
485-
The reverse doesn't work as well:
SEKLECT to_number('485-', '999S');
to_number
---
485
Is this a bug or intentional?
--
Peter Eisentraut
http://developer.postgresql.or
14 matches
Mail list logo