Tom Lane wrote:
Joe Conway <[EMAIL PROTECTED]> writes:
select 'GRANT EXECUTE ON ' || 1142::regprocedure;
ERROR: array value must start with "{" or dimension information
BTW, it seems like there's something pretty broken here. How did
arrays get into it? A quick probe suggests that it is res
Joe Conway <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Um. Sooner or later we ought to do something about the whole
>> automatic-casting-to-and-from-text issue. Datatypes shouldn't have to
>> supply both I/O procedures and text cast procedures.
> I thought automatic (i.e. implicit) casting-
Tom Lane wrote:
Um. Sooner or later we ought to do something about the whole
automatic-casting-to-and-from-text issue. Datatypes shouldn't have to
supply both I/O procedures and text cast procedures.
I thought automatic (i.e. implicit) casting-to-and-from-text was a no-no
because it could cause
Joe Conway <[EMAIL PROTECTED]> writes:
>select 'GRANT EXECUTE ON ' || 1142::regprocedure;
>ERROR: array value must start with "{" or dimension information
BTW, it seems like there's something pretty broken here. How did
arrays get into it? A quick probe suggests that it is resolving
the
Joe Conway <[EMAIL PROTECTED]> writes:
> That's even better -- I tried regproc, but forgot about regprocedure. I
> think the problem will be, though, that the output of the reg* datatypes
> is not castable to text, and therefore cannot be used to build a dynamic
> sql statement.
Um. Sooner or
Tom Lane wrote:
Also, casting the function's OID to regprocedure may be useful.
Random example:
regression=# select 1142::regprocedure;
regprocedure
date_mii(date,integer)
(1 row)
That's even better -- I tried regproc, but forgot about regprocedure. I
think the prob
Joe Conway <[EMAIL PROTECTED]> writes:
> Jean-Denis Giguere wrote:
>> But, the problem is more complex for functions because you have to give
>> the arguments.
> Does this help?
> SELECT n.nspname || '.' || p.proname ||
> '(' || pg_catalog.oidvectortypes(p.proargtypes) || ')'
Also, cast
Gaetano Mendola <[EMAIL PROTECTED]> writes:
> P.A.M. van Dam wrote:
>> I'm looking for a command or method to find out what queries are
>> currently being serviced by the database.
> select * from pg_stat_activity;
... having first remembered to turn on stats_command_string; and
thou shalt also
Werner Bohl <[EMAIL PROTECTED]> writes:
> We have a very big db that was not vacuumed for a long time. We started
> vacuum 3 days ago and it has not finished yet. There are some urgent
> processes that have to be run against the db.
> Is it safe to kill vacuum? It was started with 'vacuum full ana
unsubscribe-digest pgsql-admin
诚挚问候
--
周仁军
游戏运营二部
上海盛大网络发展有限公司
TEL:021-50504740-6124
Email:[EMAIL PROTECTED]
--
www.bfo.com.cn
--
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.gri
IIRC killing vacuums can cause some minor problems - i think it may have
(Bbeen something like index bloat. Tom said something about it once before.
(B
(BOtherwise, as I understand it, it's "safe" to kill vacuums.
(B
(BCheers
(BIain
(B
(B- Original Message -
(BFrom: "Werner Bohl"
Jean-Denis Giguere wrote:
But, the problem is more complex for functions because you have to give
the arguments. You can find the list in the pg_proc table but they are
store in a array by oid. So you can resolve the type with the table
pg_type. After, you have to reproduce the correct syntax (w
Hi,
I have about 200 functions in a schema and I have to grant execute
privilege on all these functions to a group.
I have found on the web an interesting function for grant access on table.
http://www.lerctr.org/pgnotes/pgnotes.html
(http://www.lerctr.org/pgnotes/grant-all.html)
But, the prob
P.A.M. van Dam wrote:
Hi!
I'm looking for a command or method to find out what queries are
currently being serviced by the database.
select * from pg_stat_activity;
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 6: Have you searched our list a
Jeff Keller wrote:
I had a typo in the first post. The Record Reads per day should be
50,000,000, not 500 Million. My mistake. One decimal place makes a huge
difference. Our current app is Progress based with running on an IBM p650
with 4 processors and suspect a similar load if we were to cha
Could I ask for feedback on the error messages used with the archiver
and restore functionality? Possibly those of you with a hand in the
Error Message style guide?
The messages need the eye of some administrators to suggest some better
phrases. Some probably need some explanation, but I'll leave
To speed up, consider to increase vacuum_mem if you have free RAM.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of CHRIS HOOVER
Sent: Tuesday, June 29, 2004 10:30 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [ADMIN] Stopping vacuum
It is safe
hello,
I am trying to migrate a database in PostgreSQL to
Oracle. The version of Oracle that i currently have is
Oracle 10g. Is there any open source tool or any other
way of migrating my postgresql database to Oracle.
Thank you.
Hetal.
__
Do you
It is safe to kill the vacuum (but not a favored thing to do). I have done it
many times when the vacuums have run to long and have started to affect my
online production performance. Be sure to just do a kill, as a kill -9 will
cause the db to reset all connections to it.
Since you have not vac
On Tuesday 29 June 2004 10:55, Tom Lane wrote:
> I need to re-roll those because I forgot to update the JDBC driver jars
> to the latest version :-(. But they're good as far as the other
> components go.
Once Tom has rerolled them, those RPMs shoud be considered 'canonical' for
FC2. I need to d
>[EMAIL PROTECTED] (Thomas F. O'Connell) writes:
>> I transfer this file to another server, where the database db does not
>> exist. I try the following:
>
>> pg_restore -C -d db pg_dump20040621.pgsql
>> pg_restore: [archiver (db)] connection to database "db" failed: FATAL:
>> database "db" does n
Hi,
We have a very big db that was not vacuumed for a long time. We started
vacuum 3 days ago and it has not finished yet. There are some urgent
processes that have to be run against the db.
Is it safe to kill vacuum? It was started with 'vacuum full analyze'
Is there anyway to speed it up at nex
This did finaly work for me. I have to add that to get this working it is
required to have a UTF-8 aware system on which the psql runs during import.
Since the database server is not a UTF-8 system, my tries with this approche
on the server only did fail.
Thanks a lot.
Best regards
Ivo Rossac
Hi!
I'm looking for a command or method to find out what queries are
currently being serviced by the database.
Once in a while a query goes berzerk and uses up all CPU. I'd like to
find out which query is the culprit and want to kill it off. In Sybase
you can get a list of running "processes" wi
Bruno Wolff III <[EMAIL PROTECTED]> writes:
> Donald Fraser <[EMAIL PROTECTED]> wrote:
>> does anyone know if binary versions or at least the source rpm are going to be
>> produced for the latest release 7.4.3?
> They are available for Fedora Core 2. I think they are in the development
> area.
"Nigel Bishop" <[EMAIL PROTECTED]> writes:
> pg_dump: Attempt to lock table "Foo" failed. ERROR: MySchema:
> permission denied
Looks like you need to grant yourself usage rights on the schema
"MySchema".
> If I try to drop this it errors saying the table foo doesn't exist.
Can't tell whether y
On Tue, Jun 29, 2004 at 12:27:52 +0100,
Donald Fraser <[EMAIL PROTECTED]> wrote:
> Hi,
> does anyone know if binary versions or at least the source rpm are going to be
> produced for the latest release 7.4.3?
They are available for Fedora Core 2. I think they are in the development
area. I foun
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Tue, 29 Jun 2004, Donald Fraser wrote:
> does anyone know if binary versions or at least the source rpm are going to be
> produced for the latest release 7.4.3?
I've built them:
http://www.gunduz.org/postgresql/packages-7.4.3/
Regards,
-
Hi,
does anyone know if binary versions or at least the
source rpm are going to be produced for the latest release 7.4.3?
Thanks in advance
Donald Fraser
Hi
I'm getting an error with pg_dump:
I'm using
pg_dump -v -C -U username database > ./dumpfile.dmp
and it errors with:
pg_dump: saving database definition
pg_dump: reading namespaces
pg_dump: reading user-defined types
pg_dump: reading user-defined functions
pg_dump: reading user-defined aggr
30 matches
Mail list logo
