> "Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> > We need to dump constraint name always for CHECK, or suppress default
names
> > in ADD FOREIGN KEY.
>
> Didn't Rod Taylor fix that recently?
You're quite correct - it has been fixed.
Chris
---(end of broadcast)-
> "Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> > We need to dump constraint name always for CHECK, or suppress default
names
> > in ADD FOREIGN KEY.
>
> Didn't Rod Taylor fix that recently?
Maybe - I haven't checked 7.4's dump of that yet...I'll give it a go...
Chris
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> We need to dump constraint name always for CHECK, or suppress default names
> in ADD FOREIGN KEY.
Didn't Rod Taylor fix that recently?
regards, tom lane
---(end of broadcast)--
Carlos Guzman Alvarez <[EMAIL PROTECTED]> writes:
> I'm trying to create a database using the extended query mode ( with my
> own implementation of the 3.0 protocol in C# ) but i'm having problem,
> the CREATE DATABASE command seems to be executed well and the answer of
> the server is the expec
On Sat, Jul 05, 2003 at 09:51:16PM -0400, Tom Lane wrote:
> but I haven't really thought through the details. In any case, that
> would be extra bookkeeping needed during every transaction start,
> so I'd want to see proof of a generally-useful improvement in return.
For what it's worth, we have
From: Kurt Roeckx <[EMAIL PROTECTED]>
Subject: Re: [HACKERS] PostgreSQL 7.4devel - LOG: PGSTAT: socket() failed: Invalid
argument
Date: Sun, 6 Jul 2003 18:44:35 +0200
;;; On Sun, Jul 06, 2003 at 06:30:04PM +0200, Kurt Roeckx wrote:
;;; > Try the attached patch instead.
;;;
;;; Oops, that one was
This table:
australia=# \d users_users
Table "public.users_users"
Column | Type |
Modifiers
+--+
-
userid | integer
In 7.4 CVS I believe joe users can see their own queries in
pg_stat_activity.
Chris
- Original Message -
From: <[EMAIL PROTECTED]>
To: "ivan" <[EMAIL PROTECTED]>
Cc: "pgsql-hackers list" <[EMAIL PROTECTED]>
Sent: Tuesday, July 08, 2003 4:34 AM
Subject: Re: [HACKERS] pg_stat_activity
>
This:
create user bob;
create user sue;
\c - bob
create table parent (a int4 primary key);
create table child(b int4 references parent);
\c - chriskl (I'm superuser)
alter table child owner to sue;
Now, do a dump:
pg_dump test > script.sql (attached)
And try to restore it:
bash-2.03$ psql t
> I have looked into my Linux box and found this in /usr/share/i18n/charmaps/BIG5.gz:
> % Chinese charmap for BIG5 (CP950)
> % version: 0.92
> % Contact: Tung-Han Hsieh <[EMAIL PROTECTED]>
> % Yuan-Chung Cheng <[EMAIL PROTECTED]>
> % Distribution and use is free, even for comercial purpo
> On Mon, 7 Jul 2003, Lauris Bukshis wrote:
>
> > LC_COLLATE: lv_LV.UTF-8
> > LC_CTYPE: lv_LV.UTF-8
> >
> > but when making upper or lower on any text latvian symbols stays on the
> > same case. And I can't get lower and upper to work correctly
ivan wrote:
>
> You can create function with security definer as super user
> sth like this
> create or replace function func () returns setof pg_stat_activity as '
> select * from pg_stat_activity ; ' language SQL SECURITY DEFINER;
>
> and if you want to se only query of session user you need to
You can create function with security definer as super user
sth like this
create or replace function func () returns setof pg_stat_activity as '
select * from pg_stat_activity ; ' language SQL SECURITY DEFINER;
and if you want to se only query of session user you need to replace
* to columns from
On Mon, 7 Jul 2003, Christopher Kings-Lynne wrote:
> > would be the right solution to make tsearch V2 to be fully incompatible
> > with old tsearch (so both version could live in one database) and
> > release tsearch v2 in separate directory. This way require some additional
> > work but would not
Hi ivan,
Sounds like a plan, I'll try it, many thanks!!
Still, shouldn't there be a view like this : select * from db_activity
wher it returns stat_activity only for current database??
Regaerds
On Mon, 7 Jul 2003, ivan wrote:
> Date: Mon, 7 Jul 2003 21:21:32 +0200 (CEST)
> From: ivan <[EMAIL PR
On Fri, 2003-07-04 at 13:40, Vincent van Leeuwen wrote:
> I've been using pg_autovacuum for a couple of weeks now
Glad to hear it.
> and have noticed one
> weird little bug: sometimes the daemon calculates it used a negative amount of
> time for the last vacuum it did, and waits no time at all b
Sorry for the slow response, I was away for the 4th.
On Fri, 2003-07-04 at 14:53, Christopher Browne wrote:
> Vincent Van Leeuwen wrote:
> > 2411 All DBs checked in: -717533400 usec, will sleep for 30 secs.
>
> That sure looks like a 32 bit wraparound bug;
Agreed, please check with pg_autovaccu
Hello:
I'm trying to create a database using the extended query mode ( with my
own implementation of the 3.0 protocol in C# ) but i'm having problem,
the CREATE DATABASE command seems to be executed well and the answer of
the server is the expected but the database is never created, if i exec
Hi every one,
Is there a way for joe user (not superuser) to see current query on HIS
database on pg_stat_activity.
ISTM that only superuser can see current query for all.
As fr security, it doesn't seem right that select * from pg_stat_activity
shows all databases.
What do you think?
--
Oliv
> get a chance. I don't have commit access, so Tom, shall I send a patch to
> you?
Send it to the patches list.
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
On Mon, 7 Jul 2003, Lauris Bukshis wrote:
> LC_COLLATE: lv_LV.UTF-8
> LC_CTYPE: lv_LV.UTF-8
>
> but when making upper or lower on any text latvian symbols stays on the
> same case. And I can't get lower and upper to work correctly :( Is there
>
I have postgresql 7.3.2 on Mandrake 9.1.
pg_controldata returns:
LC_COLLATE: lv_LV.UTF-8
LC_CTYPE: lv_LV.UTF-8
but when making upper or lower on any text latvian symbols stays on the
same case. And I can't get lower and upper to work correctly
I am forwarding this message to HACKERS, because on GENERAL I did not get any
answer. (Sorry for bothering in pre-relase time, I know that you are very
busy.)
-- Forwarded Message --
Subject: [GENERAL] Passing NEW to function
Date: Friday 04 July 2003 12:56
From: Darko
Patches:
int64-pqcomm.patch: changes int64_t to int64 in src/include/libpq/pqcomm.h
tested on RedHat Linux 7.3 and OSF
osf-template.patch: adds pthread support for OSF
tested on OSF (uname -a: OSF1 hostname V4.0 1229 alpha)
If these are okay, can someone apply them?
Can someone with access to di
> > Sounds to me like an obsolete version of plpgsql.so. Perhaps your
> > install failed to overwrite the previous version for some reason?
>
> Doh! Just realised I had commented out the building of plpgsql since I
had
> some non-compilable changes in there :(
And in that case I can confirm that
> Sounds to me like an obsolete version of plpgsql.so. Perhaps your
> install failed to overwrite the previous version for some reason?
Doh! Just realised I had commented out the building of plpgsql since I had
some non-compilable changes in there :(
Chris
---(end of b
Hi Ivan,
7.4CVS already supports this.
Regards,
Chris
- Original Message -
From: "ivan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 07, 2003 2:58 PM
Subject: [HACKERS] errors
>
> hi,
>
> when be meet error send string to fe. Is possible to be will send error
> no
27 matches
Mail list logo
