On Fri, 5 Sep 2003, Martin Edlman wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> > If possible, can you give a complete example script that shows the
> > problem?
>
> Here it is.
>
Unfortunately the trigger depends on some other functions that I dind't
have so I replaced those with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> If possible, can you give a complete example script that shows the
> problem?
Here it is.
CREATE OR REPLACE FUNCTION qmail_account_check() RETURNS TRIGGER AS '
-- do some check before insert/update on qmail_account
DECLARE
rec1 RECORD;
POSTGRESQL BUG REPORT TEMPLATE
Your name :Jim Michaels
Your email address :[EMAIL PROTECTED]
Syste
POSTGRESQL BUG REPORT TEMPLATE
Your name :Jim Michaels
Your email address :[EMAIL PROTECTED]
Syste
I tested this bug in 7.4beta2 and it still generates the 'create schema'
after the 'set session auth' which causes a failure upon restore.
Fortunately with the other bug I reported being fixed that gives me
the work around of just granting create on the database to the users
that own the schem
Has this been addressed?
---
Christoph Becker wrote:
> The following table was created in PostgreSQL 7.3.4
>
> create table dummy_groupmember_is_admin
> (bemerkung varchar(20));
> GRANT SELECT, UPDATE, INSERT ON dummy_group
Ben Grimm <[EMAIL PROTECTED]> writes:
> I haven't tried the 7.4 beta, so it may be fixed there - but in
> 7.3.4, pg_dumpall doesn't output global database ACL's.
This is fixed for 7.4.
regards, tom lane
---(end of broadcast)---
unsubscribe
__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
I haven't tried the 7.4 beta, so it may be fixed there - but in
7.3.4, pg_dumpall doesn't generate the commands to create schemas
in the right order. This bug may have been reported before, but
I saw no response to it in the lists.
Try this in a fresh database after an initdb:
template1=# cr
the offnum of LOCKTAG I gather indicates which row (tuple) is being
locked in a row level locking. But when I lock 2 diffrent rows of a
table, offset for both is 0. and also offset is 0 if i take a table lock
on the same table. (blkno is the same for all three locks)..shouldnt the
OffsetNumber
What a prick..
"Tom Lane" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Dinar <[EMAIL PROTECTED]> writes:
> > I thought that explain analyze doesn't execute query
>
> You thought wrong. Is the manual's explanation not clear enough?
>
> regards, tom lane
>
> ---
I haven't tried the 7.4 beta, so it may be fixed there - but in
7.3.4, pg_dumpall doesn't output global database ACL's. Try this
in a fresh database after an initdb:
template1=# create user test nocreatedb nocreateuser;
CREATE USER
template1=# create database testdb;
CREATE DATABASE
template1=#
> I have problem with foreign keys on postgresql-7.3.2-1PGDG.
>
> I have two tables, sorry for the lenght, but I want to give you complete
> information.
>
> Table qmail_account has FK on zone(name). On some occasions when I want
> to insert data to qmail_account I get the RI error that the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I have problem with foreign keys on postgresql-7.3.2-1PGDG.
I have two tables, sorry for the lenght, but I want to give you complete
information.
Table qmail_account has FK on zone(name). On some occasions when I want
to insert data
14 matches
Mail list logo
