manashi wrote:
The following bug has been logged online:
Bug reference: 2364
Logged by: manashi
Email address: [EMAIL PROTECTED]
PostgreSQL version: psql (PostgreSQ
Operating system: Linux
Description:DB Error: connect failed ... PHP/PostgreSql
This is probably *no
Bujic Nikola wrote:
The following bug has been logged online:
Bug reference: 2365
Logged by: Bujic Nikola
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: windows xp
Description:can't install
Details:
I getting mesage that postgres accoun
The following bug has been logged online:
Bug reference: 2372
Logged by: William Leite Araújo
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.7
Operating system: i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.3.5
(Debian 1:3.3.5-13)
Description:dblink_exec d
"William Leite Araújo" <[EMAIL PROTECTED]> writes:
> A trigger start a dblink_exec local connection to insert on a table "A" as
> SuperUser. Table "A" fires insert trigger that, by LOG messages, ends, but
> the function never return to initial trigger.
Perhaps the other transaction is blocked on
* Tom Lane ([EMAIL PROTECTED]) wrote:
> dblink connections to your own database are very seldom a good idea;
> there is always a better, more efficient, less deadlock-prone way
> to do it. In this case I'd venture that you want to use a SECURITY
> DEFINER function, and not dblink at all.
The one
I need this to give a credit from canceled billets. But anyone instead of roots can insert on this table. If it's done by a function, only roots must run it. So, the trigger will fail because is runned a no "su"...
On 4/3/06, Stephen Frost <[EMAIL PROTECTED]> wrote:
* Tom Lane ([EMAIL
"=?ISO-8859-1?Q?William_Leite_Ara=FAjo?=" <[EMAIL PROTECTED]> writes:
> I need this to give a credit from canceled billets.
> But anyone instead of roots can insert on this table.
> If it's done by a function, only roots must run it. So, the trigger
> will fail because is runned a no
The following bug has been logged online:
Bug reference: 2373
Logged by: Anthony Ransley
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3.6044
Operating system: Windows XP SP2
Description:postgres.exe crashes
Details:
postgres.exe craches randomly. Where c
You'll probably get better help from the windows installer folks
(there should be a mailing list somewhere on pgFoundry)... Have you
tried removing the postgres account? That would probably at least get
you running. The names and IDs thing sounds like a bug, but you'd
have to talk to the in
I fail to see how this is a bug, but...
Are you running the webserver as root? Most systems don't do that
(for good reason!). You should turn on log_connections and
log_disconnections in postgresql.conf and see what it shows is
happening (you might need to turn up log_min_messages).
On Ma
# pg8.1.3
=> CREATE DOMAIN d_1 integer CHECK (VALUE < 10);
=> CREATE TYPE t_1 AS (m d_1);
=> SELECT '(100)':: t_1;
t_1
---
(100)
(1 row)
=> SELECT row(100):: t_1;
错误: 域 d_1 的值违反了检查约束 "d_1_check"
=> \encoding ISO_8859_1
=> SELECT row(100):: t_1;
server closed the connection unexpectedly
=?UTF-8?Q?=E7=BB=B4_?= =?UTF-8?Q?=E5=A7=9C?= <[EMAIL PROTECTED]> writes:
> => \encoding ISO_8859_1
> => SELECT row(100):: t_1;
> server closed the connection unexpectedly
Works for me:
regression=# SELECT row(100):: t_1;
ERROR: value for domain d_1 violates check constraint "d_1_check"
regressio
12 matches
Mail list logo
