Hello,
using 7.4.1 on Suse 8.0.
Compiled from Source, there were no problems.
Keep care of readline-support(you need the devel-rpm
for readline), then you have more fun with psql.
The docs are a good ressource for any question regarding
instaltation.
For me it was a simple ./configure && make
Hi Richard,
Thanks for your answer. About your comments, in the original order:
1) Thanks for the links. I found in PostgreSQLs FAQ that any one can
use the database for any purpose, including comercial development. But
i couln't find if this applies to the .net driver too.
2) Yes I mean a sch
Hrishikesh Deshmukh wrote:
Hi All,
Has anybody used postgresql 7.4.7 on Suse 9.3? If yes how easy or
difficult was it to install?
Any pointers/suggestions are welcome.
No reason why it should be any more/less difficult than any other Linux
distribution.
Are there rpm's for that version on S
Am Mittwoch, den 10.08.2005, 17:38 -0400 schrieb Bruce Momjian:
> "Consider a separate column containing an MD5 hash of the value\n"
wouldnt a functional index over md5 hash of the original value
be a bit better?
---(end of broadcast)---
TIP 1: i
Dear All,
I am stuck in the following scenario:
In a dual processor machine, I am running 5
threads.
each of the threads is calling a particular stored
procedure to insert a row in the table.
the insertion takes place in a transaction and i
have set the transaction level to serializable.
Hi all,
We have a big database, around 1.2GB, and want to back it up. We used
pg_dump with --blobs for large objects. However, the process cannot
be completed and threw an error. Can anyone please elaborate on the
--blobs, or backing up for large databases? Judging from the
description of -b/-
Sorry, forgot the error message.
Basically we tried to restore a db and the following error message occurred:
pg_restore: [archiver (db)] could not execute query: ERROR: invalid
memory alloc request size 1836016426
On 8/11/05, Howard Kao <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> We have a big d
This is in
continuation of my previous mail:
each thread is using a different pgconn.
thanks again
Surabhi Ahuja
Dear All,
I am stuck in the following scenario:
In a dual processor machine, I am running 5
threads.
each of the threads is calling a particular stored
procedure to insert a ro
Howard Kao wrote:
Sorry, forgot the error message.
Basically we tried to restore a db and the following error message occurred:
pg_restore: [archiver (db)] could not execute query: ERROR: invalid
memory alloc request size 1836016426
I take it you don't have an object 1.8GBs in size?
Do you
On Thu, Aug 11, 2005 at 03:17:53PM +0530, Surabhi Ahuja wrote:
> This is in continuation of my previous mail:
> each thread is using a different pgconn.
> Please tell, in case I should provide more info in regard to this scenario?
Yes. I've no idea what your problem might be, and I'm probably
Od: Michael Fuhr <[EMAIL PROTECTED]>
..
> * More support for composite types (row and record variables) in
> PL/pgSQL
>
> For example, it now works to pass a rowtype variable to another
> function as a single variable.
>
> If you're using a version older than 8.0 then you'll have to work
> with
void
*connect(void* threadid){ char
command[100]; int *id_ptr, taskid;
id_ptr = (int *) threadid; taskid = *id_ptr;
if(taskid ==
0) strcpy(command, "select insert
(1)"); else if(taskid ==
1) strcpy(command, "select insert
(1)"); else if(taskid ==
2)
Surabhi Ahuja wrote:
void *connect(void* threadid)
{
char command[100];
int *id_ptr, taskid;
id_ptr = (int *) threadid;
taskid = *id_ptr;
if(taskid == 0)
strcpy(command, "select insert (1)");
else if(taskid == 1)
strcpy(command, "select insert (1)");
...
> I saw their announment today and they said they have Oracle compatiblility.
>
> What exactly does this mean? They don't go into any details. Did
> they implement a Oracle compatible proc language or something?
I believe you are correct.
It's probably safer to say "they have implemented a more
Al_Dev wrote:
> World-wide Stop Order on PERL,Python,Java::->> Use Ruby instead
> Al Dev
> alavoor[at]-no-spam(dot)yahoo(dot)com
There's irony for you.
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
Why yes, I am tired of spam. Thank you for asking!
Randal L. Schwartz wrote:
> > "Google" == Google Mike <[EMAIL PROTECTED]> writes:
>
> Google> As a PostgreSQL admin or developer, you may be asked to deploy a Linux
> Google> Apache PHP PostgreSQL application.
>
> Not me. I'll be deploying an OpenBSD, Apache, PostgreSQL, Perl server.
>
> o/~ y
Is the standard libpq.dll distributed by PostgreSQL8.0 for windows
thread safe by default ?
Pit
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's dataty
On Thu, Aug 11, 2005 at 12:20:17PM +0200, tgrzej wrote:
> I tried to follow #37.1.2 from:
> http://www.postgresql.org/docs/7.4/interactive/plpgsql.html
>
> where one can read:
> "Functions written in PL/pgSQL can accept as arguments any scalar or
> array data type supported by the server, and they
Tino Wildenhain wrote:
> Am Mittwoch, den 10.08.2005, 17:38 -0400 schrieb Bruce Momjian:
> > "Consider a separate column containing an MD5 hash of the value\n"
>
> wouldnt a functional index over md5 hash of the original value
> be a bit better?
Yes, good point. Let me adjust the text.
--
Br
Title: Fwd: [GENERAL] What's up with EnterpriseDB?
Once the flood gates of new features are opened
up for 8.2, we'd be happy to submit a patch for anonymous blocks. Also, if
there are other features we've added that makes since to roll back, let us know
and we could submit that as well.
Th
hi,
I'm trying to instal postgresql to support an open-source software named
dspace. I have already installed sdk, tomcat5, postgresql8.0.3, but when I
install dspace, I met error says [java] Exception:java.net.SocketException:
Invalid argument or cannot assign requested address. I think p
# [EMAIL PROTECTED] / 2005-08-11 16:04:00 +0530:
> void *connect(void* threadid)
> {
> char command[100];
> int *id_ptr, taskid;
> id_ptr = (int *) threadid;
> taskid = *id_ptr;
> if(taskid == 0)
> strcpy(command, "select insert (1)");
> else if(taskid == 1)
>
hi,
try this in pg_hba.conf ,
if the db is on the same machine:
local all all trust
if db is on another machine in the local network
hostall all "ip_of_the_machine_to_connect_from"
255.255.255.0 trust
Afterwards you n
Howard Kao <[EMAIL PROTECTED]> writes:
> Basically we tried to restore a db and the following error message occurred:
> pg_restore: [archiver (db)] could not execute query: ERROR: invalid
> memory alloc request size 1836016426
I'm wondering about corruption of the dump file. I don't think either
How does one raise an exception from a PL/Perl function? Specifically,
this is a trigger function. Is it as simple as "die "?
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
[EMAIL PROTECTED] (Jeff Boes) writes:
> Al_Dev wrote:
>> World-wide Stop Order on PERL,Python,Java::->> Use Ruby instead
>
>> Al Dev
>> alavoor[at]-no-spam(dot)yahoo(dot)com
>
> There's irony for you.
>
>> Tired of spam? Yahoo! Mail has the best spam protection around
>> http://mail.yahoo.com
>
Greetings,
I met a question about how to use *function variable *as the *table
name* to select count(*) into an integer variable for the table.
CREATE OR REPLACE FUNCTION update_code_map(VARCHAR, VARCHAR) RETURNS
VARCHAR AS $$
DECLARE
*tableName ALIAS FOR $1*;
*rec_num
On Thu, Aug 11, 2005 at 10:15:11AM -0400, Jeff Boes wrote:
> How does one raise an exception from a PL/Perl function?
> Specifically, this is a trigger function. Is it as simple as "die
> "?
elog(ERROR, $errmsg)
works.
Cheers,
D
--
David Fetter [EMAIL PROTECTED] http://fetter.org/
phone: +1 510
On Thu, Aug 11, 2005 at 10:15:11AM -0400, Jeff Boes wrote:
> How does one raise an exception from a PL/Perl function? Specifically,
> this is a trigger function. Is it as simple as "die "?
Use elog:
http://www.postgresql.org/docs/8.0/static/plperl-database.html
--
Michael Fuhr
Ying Lu wrote:
Greetings,
I met a question about how to use *function variable *as the *table
name* to select count(*) into an integer variable for the table.
Look at: FOR-IN-EXECUTE
http://www.postgresql.org/docs/8.0/static/plpgsql-control-structures.html#PLPGSQL-RECORDS-ITERATING
--
Ric
On Thu, 11 Aug 2005, Ying Lu wrote:
> Greetings,
>
> I met a question about how to use *function variable *as the *table
> name* to select count(*) into an integer variable for the table.
>
>
> CREATE OR REPLACE FUNCTION update_code_map(VARCHAR, VARCHAR) RETURNS
> VARCHAR AS $$
> DECLARE
> *ta
On Thu, 11 Aug 2005, Surabhi Ahuja wrote:
> the stored procedure (just the pseudo code)
> table x has a primary key k
> insert(integer)
> {
> select from table if k = $1
> if not found
> insert into x ($1);
> else
>insert into some_other_table($1);
> end if
>
[snip]
> He's not spam.
But anybody could easily forge his address while sending to the group.
So that makes the mail itself no less spam.
The best way to handle those mails currently is dump and ignore them.
Otherwise threads like this one pop up...
Cheers,
Csaba.
---(
Thank you all for the helping.
I made a bit changes as the following and it works.
CREATE OR REPLACE FUNCTION update_code_map(VARCHAR, VARCHAR) RETURNS
VARCHAR AS $$
DECLARE
tableName ALIAS FOR $1;
st1_tabno_value ALIAS FOR $2;
rec_num INTEGER;
query_value
I'm looking for details on the new Perl server-side language
introduced in 8.0. Specifically, I'm looking for changes between 7.4
and 8.0 and if there are any backward compatibility issues.
I checked the website and docs, but didn't find anything.
Thanks.
--
Brandon
--
On Wednesday August 10 2005 6:03 pm, Michael Fuhr wrote:
> On Wed, Aug 10, 2005 at 05:02:46PM -0600, Ed L. wrote:
> > I have two identical servers giving abysmal INSERT
> > performance in pgsql 7.3.4, 7.4.8, and 8.1devel under no
> > load or I/O contention at all (no dumps, no vacuums, no
> > apps,
Hi all-
Is there any way to disable PUBLIC access by default? When I create a
new object (table, function, etc.), it has no ACL, as expected.
However, the first time I run:
GRANT ALL ON FUNCTION foo() to GROUP developers;
Postgress seems to do:
GRANT ALL ON FUNCTION foo() to PUBLIC;
I assume
On Thursday August 11 2005 12:36 pm, Ed L. wrote:
> On Wednesday August 10 2005 6:03 pm, Michael Fuhr wrote:
> > On Wed, Aug 10, 2005 at 05:02:46PM -0600, Ed L. wrote:
> > > I have two identical servers giving abysmal INSERT
> > > performance in pgsql 7.3.4, 7.4.8, and 8.1devel under no
> > > load
I have a database with blobs, I dump it with the following command:
pg_dump\
--host=$SENSAGE_DB_HOST\
--port=$SENSAGE_DB_PORT\
-U $SENSAGE_DB_ROOT_USER\
--blobs\
--create\
--format=t\
--file="$upgrade_dump"\
$SENSAGE_DB_NAME
I then move the data directory to the side, install the new version in
On Thu, Aug 11, 2005 at 12:51:29PM -0500, Brandon Metcalf wrote:
> I'm looking for details on the new Perl server-side language
> introduced in 8.0. Specifically, I'm looking for changes between 7.4
> and 8.0 and if there are any backward compatibility issues.
>
> I checked the website and docs,
On Thu, Aug 11, 2005 at 12:28:44PM -0500, Peter Fein wrote:
> Is there any way to disable PUBLIC access by default? When I create a
> new object (table, function, etc.), it has no ACL, as expected.
> However, the first time I run:
>
> GRANT ALL ON FUNCTION foo() to GROUP developers;
>
> Postgre
On Thu, Aug 11, 2005 at 12:59:32PM -0600, Ed L. wrote:
> > Michael, you seem to have nailed it. The local inserts (via
> > Unix domain sockets?) that were running at 6 QPS ran at 6800
> > to 41000 QPS in a PL/pgSQL function.
>
> Here's another part of the riddle. The query durations for the
> i
I'm using plphp to create a trigger. I don't see any
syntax errors in it (I've checked it with php -l
(lint)). When I update a row in the table with the
trigger, I get this error:
ERROR: plphp: unable to register function
"plphp_proc_4947785_trigger"
I've verified that plphp (and plphpu) is inst
I'm getting this warning in pgsql's log:
LOG: plphp: PHP Warning: Call-time pass-by-reference
has been deprecated - argument passed by value; If
you would like to pass it by reference, modify the
declaration of [runtime function name](). If you
would like to enable call-time pass-by-reference,
m == [EMAIL PROTECTED] writes:
m> On Thu, Aug 11, 2005 at 12:51:29PM -0500, Brandon Metcalf wrote:
m> > I'm looking for details on the new Perl server-side language
m> > introduced in 8.0. Specifically, I'm looking for changes between 7.4
m> > and 8.0 and if there are any backward compatibili
Nevermind, I found some stray single quotes (in an
array var) in a double-quoted string that appears to
have been the problem.
--- CSN <[EMAIL PROTECTED]> wrote:
> I'm using plphp to create a trigger. I don't see any
> syntax errors in it (I've checked it with php -l
> (lint)). When I update a
Uh oh, I think plphp is crashing the server. When I
update a row in the table with the trigger, this
happens:
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting
res
Jeez, nevermind again! Turns out this was the problem
in the plphp script:
$sql="select * from table where id=123";
$result=spi_exec_query($sqll);
I'm still curious about the "Call-time
pass-by-reference has been deprecated" warning if
anybody knows.
Thanks,
CSN
--- CSN <[EMAIL PROTECTED]> wr
On Thu, Aug 11, 2005 at 01:50:21PM -0700, CSN wrote:
> And this is what shows up in the log:
>
> LOG: server process (PID 31665) was terminated by
> signal 11
> LOG: terminating any other active server processes
>
> Wow. I still don't see anything wrong with the plphp
> function - how could it
On Thursday August 11 2005 1:37 pm, Michael Fuhr wrote:
> Have you done any client-side tests that eliminate Perl? I'd
> suggest writing a little C program so you can measure libpq's
> performance without the extra layers of Perl and DBI/DBD::Pg.
> Test both local (Unix socket) and network (IPv4
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Actually, that last grant is implicit. When an ACL is found to be null,
> it's considered to have a grant to public.
No, it's considered to be whatever the default for the object type is.
Read the GRANT manual page.
regards, to
Christian Goetze <[EMAIL PROTECTED]> writes:
> pg_restore\
> --host=$SENSAGE_DB_HOST\
> --port=$SENSAGE_DB_PORT\
> -U $SENSAGE_DB_ROOT_USER\
> --create\
> --format=t\
> "$upgrade_dump"
> Seems to work fine, except I get:
> pg_restore: [archiver] WARNING: skipping large-object restoration
IIRC, y
Peter Fein wrote:
> Hi all-
>
> Is there any way to disable PUBLIC access by default? When I create
You can revoke permissions from the public schema, and you can even
delete the public schema entirely. I did the first:
revoke create on schema public from public
revoke create on tablespace pg_
pg_restore: [archiver] WARNING: skipping large-object restoration
IIRC, you get that if you're asking it to emit a text script rather than
connect directly to the destination database server. I think you need a
"-d databasename" switch to make that happen.
Does this mean that
>
> Michael, you nailed it again. My libpq test C program delivered
> between 2400 QPS and 5000 QPS vs ~10 QPS for DBI/DBD::Pg on this
> box.
>
> It remains unclear to me why the same DBI/DBD::Pg client code
> would deliver performance 2-3 orders of magnitude better on
> other roughly comparabl
Christian Goetze <[EMAIL PROTECTED]> writes:
>>> pg_restore: [archiver] WARNING: skipping large-object restoration
>>
>> IIRC, you get that if you're asking it to emit a text script rather than
>> connect directly to the destination database server. I think you need a
>> "-d databasename" switch
# [EMAIL PROTECTED] / 2005-08-11 13:23:52 -0700:
> I'm getting this warning in pgsql's log:
>
> LOG: plphp: PHP Warning: Call-time pass-by-reference
> has been deprecated - argument passed by value; If
> you would like to pass it by reference, modify the
> declaration of [runtime function name]
Roman Neuhauser wrote:
# [EMAIL PROTECTED] / 2005-08-11 13:23:52 -0700:
I'm getting this warning in pgsql's log:
LOG: plphp: PHP Warning: Call-time pass-by-reference
has been deprecated - argument passed by value; If
you would like to pass it by reference, modify the
declaration of [runtime
# [EMAIL PROTECTED] / 2005-08-11 15:45:18 -0700:
> Roman Neuhauser wrote:
> ># [EMAIL PROTECTED] / 2005-08-11 13:23:52 -0700:
> >
> >>I'm getting this warning in pgsql's log:
> >>
> >>LOG: plphp: PHP Warning: Call-time pass-by-reference
> >>has been deprecated - argument passed by value; If
> >>
Hello,
I currently running an update statement that updates every row in a
very large table. This query will obviously take a long time to run.
My question -- is there any way to know how much time it will take
once it starts? Even something that could help me approximate the
speed at which it's
# [EMAIL PROTECTED] / 2005-08-11 16:17:09 -0700:
> Hello,
> I currently running an update statement that updates every row in a
> very large table. This query will obviously take a long time to run.
> My question -- is there any way to know how much time it will take
> once it starts? Even someth
I'm using PHP5, and I'm not passing by reference. My
first stop WAS plphp.commandprompt.com, but none of
their mailing list links for plphp work.
CSN
> # jd ( at ) commandprompt ( dot ) com / 2005-08-11
15:45:18 -0700:
> > Roman Neuhauser wrote:
> > ># cool_screen_name90001 ( at ) yahoo ( dot )
# [EMAIL PROTECTED] / 2005-08-11 16:49:25 -0700:
> I'm using PHP5, and I'm not passing by reference. My
> first stop WAS plphp.commandprompt.com, but none of
> their mailing list links for plphp work.
Can you post the code that triggers the warning?
--
How many Vietnam vets does it take to s
Akash Garg <[EMAIL PROTECTED]> writes:
> I currently running an update statement that updates every row in a
> very large table. This query will obviously take a long time to run.
> My question -- is there any way to know how much time it will take
> once it starts? Even something that could help
Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
>
>>Actually, that last grant is implicit. When an ACL is found to be null,
>>it's considered to have a grant to public.
>
>
> No, it's considered to be whatever the default for the object type is.
> Read the GRANT manual page.
I'm o
On Thu, Aug 11, 2005 at 03:29:29PM -0600, Ed L. wrote:
> Michael, you nailed it again. My libpq test C program delivered
> between 2400 QPS and 5000 QPS vs ~10 QPS for DBI/DBD::Pg on this
> box.
>
> It remains unclear to me why the same DBI/DBD::Pg client code
> would deliver performance 2-3 o
Peter Fein <[EMAIL PROTECTED]> writes:
> If I read my ACL's correctly, =UC/postgres means full access for PUBLIC.
> Why is that happening?
Because that's the way it's set up in template1. CREATE DATABASE just
copies the source database, it doesn't editorialize on the contents
thereof.
I have tried different options to turnoff the output mode of
psql (turning off the STDERR & STDOUT and redirecting it to another file),
and I have not been successful. The steps I have taken to capture the output of
my script in an output file using the ‘\o’ option, are as follows:
# \o
Sure-
CREATE or REPLACE FUNCTION email_activated_member ()
RETURNS trigger AS $$
$new=$_TD['new'];
$old=$_TD['old'];
if(($_TD['event']=='INSERT' and $new['active']='t') or
($_TD['event']=='UPDATE' and $new['active']=='t' and
$old['active']=='f')) {
$link=$_TD['new'];
$sql="select *
fr
CSN wrote:
I'm using PHP5, and I'm not passing by reference. My
first stop WAS plphp.commandprompt.com, but none of
their mailing list links for plphp work.
You are correct. This is a mistake on our part. Perhaps next time
a little note to support or info@ saying, "Hey what is up with this l
# [EMAIL PROTECTED] / 2005-08-11 17:36:49 -0700:
> --- Roman Neuhauser <[EMAIL PROTECTED]> wrote:
> > Can you post the code that triggers the warning?
>
> Sure-
>
>
> CREATE or REPLACE FUNCTION email_activated_member ()
> RETURNS trigger AS $$
>
> $new=$_TD['new'];
> $old=$_TD['old'];
>
>
--- Roman Neuhauser <[EMAIL PROTECTED]> wrote:
> # [EMAIL PROTECTED] / 2005-08-11
> 17:36:49 -0700:
> > --- Roman Neuhauser <[EMAIL PROTECTED]> wrote:
> > > Can you post the code that triggers the
> warning?
> >
> > Sure-
> >
> >
> > CREATE or REPLACE FUNCTION email_activated_member
> ()
>
Roman Neuhauser <[EMAIL PROTECTED]> writes:
> Yeah, it would be nice if select, insert, update, delete could
> be set to log their progress at configured intervals.
One feature that would be handy for doing this would be if Postgres supported
READ DIRTY. Few databases support it, and Pos
Michael Fuhr napisal(a):
PL/pgSQL functions can *accept* these types of arguments, but in
versions earlier than 8.0 they have trouble *passing* such arguments
to another function.
Now I get it. Thank you.
Tomek Grzejszczyk
---(end of broadcast)---
Greg Stark <[EMAIL PROTECTED]> writes:
> One feature that would be handy for doing this would be if Postgres supported
> READ DIRTY. Few databases support it, and Postgres currently doesn't, but it
> would be extremely handy for peeking to see how much progress an update,
> delete, or insert has ma
75 matches
Mail list logo
