Fabien COELHO <[EMAIL PROTECTED]> writes:
> So the only problem is to implement system-wide "cluster" sequences...
We certainly can't extend the regular CREATE SEQUENCE command this way;
you can't create shared objects after initdb.
The "clean" way to handle this would be to extend the bootstrap
Sean Chittenden wrote:
> In a follow up to my post from two days ago about creating TEMP TABLES,
> I noticed what I think is kind of a glaring omission: CREATE TEMP TABLE
> AS doesn't support ON COMMIT. Nothing Earth shattering, but it did
> catch me by surprise. There's also no ALTER TABLE st
Martin Pitt <[EMAIL PROTECTED]> writes:
> (gdb) bt
> #0 0x402e675e in getc () from /lib/tls/i686/cmov/libc.so.6
> #1 0x0814142d in next_token (fp=3D0xbfffde4c, buf=3D0xbfffde54 "", bufsz=
> =3D1109025003) at hba.c:102
> #2 0x4217ecb5 in str_list_make () from /lib/libnss_wins.so.2
> #3 0x421310b
Hi!
On 2004-06-08 11:18 -0400, Tom Lane wrote:
> Can you try again to get a debugger stack trace? Maybe with the patch
> there'll be a more sensible stack...
I am now able to reproduce this bug. I installed package 'winbind' and
changed the hosts line in /etc/nsswitch.conf to
hosts:
On Tue, Jun 08, 2004 at 05:27:31PM +0200, Fabien COELHO wrote:
> From a practical point of view, I wish I could download all messages from
> this thread so as to do the reading in my mail user agent. Does not seem
> possible from the web interface I found.
No, there is no interface to get the m
Erwin Brandstetter <[EMAIL PROTECTED]> writes:
> # While running with:
> lc_messages = 'de_AT'
> encoding = UNICODE
> psql:./e_schema.sql:157: FEHLER: could not convert UTF-8 character
> 0x00fc to ISO8859-1
> psql:./e_schema.sql:159: FEHLER: Relation »naehe« existiert nicht
> There seems to be
Hello!
I have posted the following a week ago, but it was stalled as I was not
subscribed to pgsql-bugs. As it has not entered the list yet, I repost
after subsribing, assuming my mail has been eaten by the spam-filters.
I ported a PostgreSQL database to a new server. Dump from old server
shoul
"Daniel O'Neill" <[EMAIL PROTECTED]> writes:
> Anyway, here's the vitals, including our layout:
Could I trouble you to provide those table and view definitions as an
SQL script? (pg_dump -s will help you.) I'm too short of time to
manually convert your \d listings into something executable.
Dear Tom.
(I have some vague recollection that we discussed how to do that during
the last go-round --- if you want to work on this, it'd be a good idea
to look in the archives first.)
Ok. I found a thread initiated by you in january 2003. I read it quickly.
From a practical point of view, I wish
Martin Pitt <[EMAIL PROTECTED]> writes:
> For your convenience I wrote these hex sequences into two files
> 'token1' and 'token2' and tar.gz'ed them.
Mph ... no obvious pattern here.
$ od -t x1 token1
000 98 6e 2 41 91 31 f8 40
010
$ od -t x1 token2
000 98 e3 ed 40 9
Fabien COELHO <[EMAIL PROTECTED]> writes:
> The actual simple fix would be that user ids should NOT be reused by
> default. The problem is that I don't think the already used userids are
> kept anywhere, even as a sequence.
In the last discussion of this issue, I think we had agreed in principle
I just want the system to remove the 102, since it is of no use.
I understood that.
As I said, I haven't thought about it in-depth, but keeping the permissions
with the numeric user is a bad idea.
It is only a bad idea if the same numerical user id is reused. If not,
this is not really a problem.
Hi all.
Interesting result when migrating from 7.2.? to 7.4.1, the dump and import went fine,
no errors or whistles, in fact all my tests went through okay but a few types of
queries which once worked, now don't, and in an odd fashion.
When I checked out the mailing lists and changelogs (in cvs
Hi,
since the dropped user is very unlikely to be resurrected, the correct
answer would be to remove all dangling permissions on the existing
objects. Using a sequence would only clutter the system with unused
grants.
What about ownership? would that mean you want to delete the object?
Since DR
Hi Tom!
On 2004-06-08 1:24 -0400, Tom Lane wrote:
> I didn't expect the failure to go away, only the consequent core dump.
I also hoped that the missing string termination caused the segfault,
but obviously it didn't (it was only a read operation after all).
> We still need to learn why winbind
Hello Martin,
Bug reference: 1161
Logged by: Martin
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: Linux
Description:User permissions are kept, even if user is dropped
Details:
dropping and creating a user will keep the *old* permission on ob
16 matches
Mail list logo
