On Wed, Jul 15, 2009 at 10:59 PM, Raji Sridar (raji) wrote:
> Hi,
>
> We use a typical counter within a transaction to generate order sequence
> number and update the next sequence number. This is a simple next counter -
> nothing fancy about it. When multiple clients are concurrently accessing
>
Hello. Thank you for your interesting.
Any person know that how to db export XML file in PostgreSQL? I use Ver. 8.4
and Operating System Linux. Have a nice day.
I'm not sure I understand your question.
Do you want to export the data of your database into a (single?) XML file,
or do you want to ex
Steve Choi, 16.07.2009 07:43:
Hello. Thank you for your interesting.
Any person know that how to db export XML file in PostgreSQL?
I use Ver. 8.4 and Operating System Linux. Have a nice day.
I'm not sure I understand your question.
Do you want to export the data of your database into a (
Hello. Thank you for your interesting.
Any person know that how to db export XML file in PostgreSQL?
I use Ver. 8.4 and Operating System Linux. Have a nice day.
Raji Sridar (raji) wrote:
Hi,
We use a typical counter within a transaction to generate order
sequence number and update the next sequence number. This is a simple
next counter - nothing fancy about it. When multiple clients are
concurrently accessing this table and updating it, under exter
2009/7/16 Raji Sridar (raji) :
> Hi,
>
> We use a typical counter within a transaction to generate order sequence
> number and update the next sequence number. This is a simple next counter -
> nothing fancy about it. When multiple clients are concurrently accessing
> this table and updating it, u
Hi,
Are you using automatic sequence increment in table?
- Original Message -
From: Raji Sridar (raji)
To: pgsql-general@postgresql.org ; pgsql-performa...@postgresql.org
Sent: Thursday, July 16, 2009 10:29 AM
Subject: [PERFORM] Concurrency issue under very heay loads
Hi,
Hi,
We use a typical counter within a transaction to generate order sequence number
and update the next sequence number. This is a simple next counter - nothing
fancy about it. When multiple clients are concurrently accessing this table
and updating it, under extermely heavy loads in the syst
On Jul 16, 8:05 am, t...@sss.pgh.pa.us (Tom Lane) wrote:
> CG writes:
> > While transitioning from 8.1 to 8.4, I need to transition to the internal
> > UUID type in place of the contrib/uniqueidentifier module. I've built the
> > database around uniqueidentifier, so nearly every table has one co
The same command worked fine on PG 8.2.4.
Now, using 8.3.7, we are forced into WIN1252.
Thanks
Danny
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Hi,
I recognized in psql using the internal help (\?) that the *+* sign is
missing for the shortcut \du:
# \du
List of roles
Role name | Attributes | Member of
--+--+---
# \du+
List of roles
Role name | Attributes
CG writes:
> While transitioning from 8.1 to 8.4, I need to transition to the internal
> UUID type in place of the contrib/uniqueidentifier module. I've built the
> database around uniqueidentifier, so nearly every table has one column of
> that data type. It's going to be tedious to
> ALTER
This is more a request for other folks and their experience. We have
been running Centos 5.2 in production for nearly a year with little or
no issues. The kernel it came with was 2.6.18-92.el5. About two
months ago I updated one of our to servers to 5.3, and the new kernel
is 2.6.18-128.1.14.el5
On Wed, Jul 15, 2009 at 12:05 PM, John R Pierce wrote:
> we have an app thats doing massive amounts of inserts, batched in
> transactions, multiple concurrent connections (tuned for optimal throughput,
> usually around 1 thread per cpu core plus a couple more). occasionally a
> transaction gets d
Actually the command is:initdb --encoding=LATIN1.
It fails on Windos. fails on Windows
The same command worked fine on PG 8.2.4.
Now, using 8.3.7, the command succeeds only with encoding 1252.
It comments something on wrong lc_ctype.
Thanks
Danny
--
Sent via pgsql-general mailing list (p
Hello
it's look like problem with casting. You defined function
name(integer,...) but you call it with bigint param. Bigint cannot be
casted to int - so you have to redefine your func - name(bigint, ...
regards
Pavel Stehule
2009/7/15 dipesh mistry (Imap) :
> Hello,
>
> I have create my own func
Do you by chance know what is the ISO88591 locale to be used on Windows?
It should be something like Americam_United States.ISO88591.
Thanks
Danny
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
Another UUID question... I was hoping to put this off for a while, but it looks
like it's going to need to happen sooner than later. Rats! I keep telling
myself transitioning to core datatypes is good for the soul.
While transitioning from 8.1 to 8.4, I need to transition to the internal UUID
t
dipesh mistry (Imap) wrote:
Hello,
I have create my own function name "*addnewuser(integer,varchar.)*",
and when I call this function it gives me below error,
org.postgresql.util.PSQLException: ERROR: function addnewuser(bigint,
character varying, character varying, character varying, char
In response to Florian Chis :
>
> I'm working on a port from mysql to postgres. I have a function which
> connect's to the database, checks for database existance and creates it
> otherwise.
> The last thing it does it executes "use my_database" (mysql stuff). Now I'm
> trying to find something si
OK, I figured some things out. Lines numbers are shown through PL/Python
if it is a syntax error, but not for a runtime error. I'm not sure if
this is because plpython.c only returns a partial stack trace, or what.
The 6 year old TODO list doesn't mention this (but does mention that
array argum
John R Pierce wrote:
> we have an app thats doing massive amounts of inserts, batched in
> transactions, multiple concurrent connections (tuned for optimal
> throughput, usually around 1 thread per cpu core plus a couple more).
> occasionally a transaction gets duplicated, and that causes a
On Wed, 2009-07-15 at 11:36 +0300, Florian Chis wrote:
> I'm working on a port from mysql to postgres. I have a function which
> connect's to the database, checks for database existance and creates
> it otherwise.
> The last thing it does it executes "use my_database" (mysql stuff).
> Now I'm tryin
we have an app thats doing massive amounts of inserts, batched in
transactions, multiple concurrent connections (tuned for optimal
throughput, usually around 1 thread per cpu core plus a couple more).
occasionally a transaction gets duplicated, and that causes a constraint
violation which cau
Hi,
I'm working on a port from mysql to postgres. I have a function which
connect's to the database, checks for database existance and creates it
otherwise.
The last thing it does it executes "use my_database" (mysql stuff). Now I'm
trying to find something similar in postgres. I know that psql ha
CG wrote:
> I could add the explicit type casts, but I'd rather find out what the
> nature of the subtle (or not-so-subtle) difference I've stumbled upon
> is...
It's an intentional change, so adding typecasts is the appropriate
solution.
--
Alvaro Herrerahttp://
Hello,
I have create my own function name "*addnewuser(integer,varchar.)*",
and when I call this function it gives me below error,
org.postgresql.util.PSQLException: ERROR: function addnewuser(bigint,
character varying, character varying, character varying, character
varying, character var
I'm in the process of attempting to upgrade from 8.1 to 8.4, and I've been
using the uniqueidentifier contrib module for my UUID's ... In 8.1 Postgresql
was able to figure out what to do with statements like
# SELECT 'Your new UUID is ' || newid();
?column?
---
"Abraham, Danny" writes:
Yeah, it should fail. LATIN1 is not a locale name.
> The same command worked fine on PG 8.2.4.
If so, that was a bug in 8.2.
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subsc
Hi.
Is anyone aware of a connection pool or load balancer for PostgreSQL
that supports ident based authentication? Neither pgpool-ii nor
pgbouncer support this according to their docs, so I was wondering
what else is out there.
--
Stuart Bishop
http://www.stuartbishop.net/
--
Sent via pgsql-g
This solved my problem. Now why didn't I think of that!? Thank you very
much everybody. This list is an incredible resource.
-Clark
> AFAICS, changing it to ORDER BY part_number,priority would solve the
> stated problem. If you really need the final result in priority rather
> than part numb
The same command worked fine on PG 8.2.4.
Now, using 8.3.7, the command succeeds only with locale 1252.
It comments something on wrong lc_ctype.
Any idea?
Thanks
Danny
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgr
On Wed, 2009-07-15 at 14:13 +0200, Rafael Martinez wrote:
> Hello
>
> Should not the execution of pg_stat_reset() reset *all* statistics
> counters everywhere in the database?
It only resets the stats for the current database, not the cluster wide
stats - pg_database is cluster wide.
--
Brad Ni
Brad Nicholson wrote:
> On Wed, 2009-07-15 at 14:13 +0200, Rafael Martinez wrote:
>> Hello
>>
>> Should not the execution of pg_stat_reset() reset *all* statistics
>> counters everywhere in the database?
>
> It only resets the stats for the current database, not the cluster wide
> stats - pg_datab
Rafael Martinez wrote:
> But when we execute pg_stat_reset() in our databases, not all values
> reported by pg_stat_database get updated. tup_returned, tup_fetched,
> tup_inserted, tup_updated and tup_deleted still have the old values
> after running pg_stat_reset().
>
> Am I missing anything?
>
Hello
Should not the execution of pg_stat_reset() reset *all* statistics
counters everywhere in the database?
We would like to use the numbers in pg_stat_database together with
pg_postmaster_start_time() to find out the average values per second of
some of the columns in this view.
But when we e
36 matches
Mail list logo
