"Amit Phatarphekar" <[EMAIL PROTECTED]> writes:
> I'm using Version-8.1.4 and JDBC-3 jar
> ...
> It would be nice if I can somehow know the value of $1 passed in.
This is fixed in 8.2 and up.
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgre
Ivan Sergio Borgonovo wrote:
Building up a temp table and returning a "setof record"
You can avoid the temp table and return `setof record'. Just `RETURN
NEXT temp_result' after each test, where temp_result is your declared
working variable. When you're done with all tests, do the final RETURN.
I'm using Version-8.1.4 and JDBC-3 jar
I call a db function from my java code, using a prepared statement.
When I look at the logs of postgres in data/pg_log, the statement
executed appears like for example
"select * from get_user($1)"
It would be nice if I can somehow know the value
Ivan Sergio Borgonovo <[EMAIL PROTECTED]> writes:
> for _row in
> select err, msg from errortable where err in (errcode)
> where errcode is an array.
> That syntax doesn't work...
In recent PG releases it will work as "WHERE err = ANY (errcode)"
but note that there is *no* guarantee that th
Ivan Sergio Borgonovo wrote:
I'm still investigating on how to return array elements.
I came out with something like:
create or replace function auz(out _errcode int, out _errmsg text)
returns setof record as $$
declare
errcode int[];
errmsg text[];
_row record;
begin
Ross Boylan wrote:
I'm not a DB admin; I only play one on my computer. I clearly need to
figure out how to get regular vacuum, analyze, and reindexing going (if
they aren't going already).
Thanks for all your help.
Ross
1. optimize your sql queries and 'understand' index usage,don't inde
>-Original Message-
>From: Ross Boylan [mailto:[EMAIL PROTECTED]
>Sent: Monday, 31 March 2008 0:23
>To: Joris Dobbelsteen
>Cc: [EMAIL PROTECTED]; pgsql-general@postgresql.org
>Subject: RE: [GENERAL] database 1.2G, pg_dump 73M?!
>
>
>On Sun, 2008-03-30 at 22:59 +0100, Joris Dobbelsteen wrot
On Sun, 2008-03-30 at 22:59 +0100, Joris Dobbelsteen wrote:
> >-Original Message-
> >From: Ross Boylan [mailto:[EMAIL PROTECTED]
> >Sent: Sunday, 30 March 2008 23:43
> >To: Joris Dobbelsteen
> >Cc: [EMAIL PROTECTED]; pgsql-general@postgresql.org
> >Subject: Re: [GENERAL] database 1.2G, pg
>-Original Message-
>From: Ross Boylan [mailto:[EMAIL PROTECTED]
>Sent: Sunday, 30 March 2008 23:43
>To: Joris Dobbelsteen
>Cc: [EMAIL PROTECTED]; pgsql-general@postgresql.org
>Subject: Re: [GENERAL] database 1.2G, pg_dump 73M?!
>
>On Sun, 2008-03-30 at 21:22 +0200, Joris Dobbelsteen wrote
I'm still investigating on how to return array elements.
I came out with something like:
create or replace function auz(out _errcode int, out _errmsg text)
returns setof record as $$
declare
errcode int[];
errmsg text[];
_row record;
begin
errcode[1]:=1;
er
On Sun, 2008-03-30 at 21:22 +0200, Joris Dobbelsteen wrote:
> From the top contenders, about half are indexes, so you are stuck
> with
> ~200 MB of data in the tables.
> Postgresql has some wasted space due to placement of the tuples in a
> block and overhead for each block and row. I don't kno
Kevin Hunter <[EMAIL PROTECTED]> writes:
> At 3:50p -0400 on Sat, 29 Mar 2008, Tom Lane wrote:
>> The code appears to want 700 and ownership equal to that of the
>> process executing libpq, ie, the apache server.
> I just checked the 8.3 documentation and didn't see any mention of
> the private ke
I've a plpgsql function that execute some tests on data and it has to
return which test failed.
It would be handy to return an array... but an array is returned as a
serialised object and I'd like to avoid to un-serialise it from php.
Building up a temp table and returning a "setof record" or
bui
Ross Boylan <[EMAIL PROTECTED]> writes:
> reindexing had a huge effect.
So the indexes were indeed bloated. There are some known usage patterns
in which regular vacuum isn't very good at reclaiming space in b-tree
indexes. For example if you make daily entries in an index by date and
later remov
Ross Boylan wrote:
On Sun, 2008-03-30 at 20:27 +0200, Joris Dobbelsteen wrote:
Ross Boylan wrote:
I have a postgres server for which du reports
1188072 /var/lib/postgresql/8.2/main
on Linux system.
The server has only one real database, which is for bacula. When I dump
the database, i
On Mon, Mar 31, 2008 at 05:37:26AM +1100, Naz Gassiep wrote:
> I've just installed that locale on my system (Debian Sarge). However I'm
> still getting the error. I only set the locale for that user, could it
> be that the locale needs to be set to UTF8 system wide? Here's the output:
The locale
On Sun, 2008-03-30 at 20:27 +0200, Joris Dobbelsteen wrote:
> Ross Boylan wrote:
> > I have a postgres server for which du reports
> > 1188072 /var/lib/postgresql/8.2/main
> > on Linux system.
> > The server has only one real database, which is for bacula. When I dump
> > the database, it's
Craig Ringer <[EMAIL PROTECTED]> wrote:
Past discussion here suggests that the backends are strictly single
threaded. While you might be able to use multiple threads - I don't know
- I expect you'd need to protect all SPI access by a lock that
serialized everything anyway.
Doing it external
Short answer is: use en_AU.UTF-8 for your locale. If it doesn't exist
you can create it using /etc/locale.gen (assuming you're running some
kind of linux)
I've just installed that locale on my system (Debian Sarge). However I'm
still getting the error. I only set the locale for that user,
A. Kretschmer <[EMAIL PROTECTED]> wrote:
> Maybe a solution.
>
> Please, learn to quote.
Sorry for the quoting. I guess this probably won't be OK too :-)
Strange thing about this is that there is no simple way to use
more CPUs for one function. It can be done with external functions
but why
Ross Boylan wrote:
I have a postgres server for which du reports
1188072 /var/lib/postgresql/8.2/main
on Linux system.
The server has only one real database, which is for bacula. When I dump
the database, it's 73Mg.
This is immediately after I did a full vacuum and restarted the server.
Also,
PG 8.3 has strict rule what CTYPE and LOCALLE is allowed. It is protection
before possible problems with data processing. You probably need set en_AU.uft8
locale when you initialize server.
Zdenek
Naz Gassiep napsal(a):
I have just attempted to upgrade to 8.3.1 and I now get t
On Sat, Mar 29, 2008 at 4:53 PM, Daniel Verite <[EMAIL PROTECTED]> wrote:
> Scott Marlowe wrote:
>
> > How do you do cross db access within a transaction?
> > You can't, and it's not likely that any code will be put in place to
> do this.
>
> But wasn't such code announced in 8.1? From
On Mon, Mar 31, 2008 at 04:32:16AM +1100, Naz Gassiep wrote:
> I have never bothered with the server's locale, all the locale handling
> in the app gets handled within the DB itself. I guess I now have to dig
> into the murky world of system locales and how they affect my app
> ecosystem. I don'
am Sun, dem 30.03.2008, um 18:18:45 +0200 mailte [EMAIL PROTECTED] folgendes:
> What about some C dynamically loaded function in which I could call new
> connection for each thread?
Maybe a solution.
Please, learn to quote.
Andreas
--
Andreas Kretschmer
Kontakt: Heynitz: 035242/47150, D1:
I have just attempted to upgrade to 8.3.1 and I now get this error when
trying to create a UTF8 DB:
[EMAIL PROTECTED]:~$ createdb twerl -E utf8
createdb: database creation failed: ERROR: encoding UTF8 does not match
server's locale en_AU
DETAIL: The server's LC_CTYPE setting requires encodin
[EMAIL PROTECTED] wrote:
What about some C dynamically loaded function in which I could call new
connection for each thread?
Past discussion here suggests that the backends are strictly single
threaded. While you might be able to use multiple threads - I don't know
- I expect you'd need to
I have a postgres server for which du reports
1188072 /var/lib/postgresql/8.2/main
on Linux system.
The server has only one real database, which is for bacula. When I dump
the database, it's 73Mg.
This is immediately after I did a full vacuum and restarted the server.
Also,
bacula=> SELECT reln
Tino Wildenhain wrote:
Chris Browne wrote:
...
pg_ctl is really more like the scripts in /etc/init.d; whatever it
"ought" to be called instead, I don't think "safe_postgresqld" is
it...
eek. where is that save_ something coming from?
From safe_mysqld , I imagine. I never understood the ration
> Původní zpráva
> Od: Andreas Kretschmer <[EMAIL PROTECTED]>
> Předmět: Re: [GENERAL] postgreSQL multithreading
> Datum: 30.3.2008 17:39:02
>
> [EMAIL PROTECTED] <[EMAIL PROTECTED]> schrieb:
>
> > Hi all,
> >
> > I was trying to f
[EMAIL PROTECTED] <[EMAIL PROTECTED]> schrieb:
> Hi all,
>
> I was trying to find some way to implement multithreading into my postgreSQL
> stored functions.
>
> The thing is, that I have data stored in multiple tables - for each day one
> table - and I want to write
> a function which selects
Hi all,
I was trying to find some way to implement multithreading into my postgreSQL
stored functions.
The thing is, that I have data stored in multiple tables - for each day one
table - and I want to write
a function which selects data from these tables and stores them into files (or
just ret
Chris Browne wrote:
...
pg_ctl is really more like the scripts in /etc/init.d; whatever it
"ought" to be called instead, I don't think "safe_postgresqld" is
it...
eek. where is that save_ something coming from? Apache uses
apachectl which seems pretty forward - pg_ctl seems to be in
the same s
Tom Lane wrote:
This is not entirely out of the question, because of the designed-in
property that a freshly initialized page is only inserted into by
the backend that got it --- no one else will know there is any
free space in it until VACUUM first passes over it. So if there
are a lot of diff
34 matches
Mail list logo
