On Tue, Jul 01, 2008 at 10:02:39AM -0500, Felipe de Jesús Molina Bravo wrote:
Hi
what can i do for a SRF written in C, can called as follow:
select * from obtAscendencia('(11099,15685)','(6808,9621)');
I can call the function:
select obtAscendencia('(11099,15685)','(6808,9621)');
Tom Lane wrote:
Roberts, Jon [EMAIL PROTECTED] writes:
Version: PostgreSQL 8.3.0, compiled by Visual C++ build 1400
Well, there are plenty of known bugs in 8.3.0 by now. You really
should update before complaining, not after.
Yes. And the traditional question should be asked - is there any
What does this mean and how can it be fixed? We are running Hibernate with
PostgreSQL 8.3.x...
Regards,
BTJ
--
---
Bjørn T Johansen
[EMAIL PROTECTED]
Magnus Hagander [EMAIL PROTECTED] writes:
Tom Lane wrote:
Another problem is that postmaster children that do
PGSharedMemoryDetach will still have valid inherited handles for
the shmem segment --- does that factor into the behavior? It looks
to me like the CloseHandle ought to be in
Tom Lane wrote:
Magnus Hagander [EMAIL PROTECTED] writes:
Tom Lane wrote:
Another problem is that postmaster children that do
PGSharedMemoryDetach will still have valid inherited handles for
the shmem segment --- does that factor into the behavior? It looks
to me like the CloseHandle ought
Magnus Hagander [EMAIL PROTECTED] writes:
Tom Lane wrote:
But the syslogger process (and maybe others) is *not* supposed to die.
Right. But are you saying we actually want to start up a new backend in
a directory where we already have a running syslogger (and maybe others)
processes, just no
Bjørn T Johansen wrote:
What does this mean and how can it be fixed? We are running Hibernate
with PostgreSQL 8.3.x...
What query is Hibernate generating? That's an error from the planner.
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-general mailing list
Can someone shed some light on what's happening here?
D:\backupspg_dump -Z 9 -Fc -C -U postgres -f sheepcrc\dbback.dmp sheepcrc2
pg_dump: Dumping the contents of table uploadeddatafiles failed:
PQgetCopyData
() failed.
pg_dump: Error message from server: lost synchronization with server:
got
OK, I'll try to come up with something. Do you have a recommended way of
capturing the amount memory being used by Postgres related to this? I
was
thinking I would have a plpgsql function that loops a large number of
times, calling a few xpath() calls,
Yeah, that's what I'd try first.
Richard Huxton wrote:
Bjørn T Johansen wrote:
What does this mean and how can it be fixed? We are running Hibernate
with PostgreSQL 8.3.x...
What query is Hibernate generating? That's an error from the planner.
It does sound like you're trying to query back more than 1664 columns in
one
=?UTF-8?Q?Bj=C3=B8rn?= T Johansen [EMAIL PROTECTED] writes:
What does this mean and how can it be fixed?
Reduce the number of columns in your SELECTs?
This whiffs to me of excruciatingly bad schema design. How could you
possibly need upwards of a thousand columns in a query result?
IMHO
On Wed, 02 Jul 2008 09:03:04 +0200
Magnus Hagander [EMAIL PROTECTED] wrote:
Richard Huxton wrote:
Bjørn T Johansen wrote:
What does this mean and how can it be fixed? We are running Hibernate
with PostgreSQL 8.3.x...
What query is Hibernate generating? That's an error from the
Magnus Hagander wrote:
Richard Huxton wrote:
Bjørn T Johansen wrote:
What does this mean and how can it be fixed? We are running Hibernate
with PostgreSQL 8.3.x...
What query is Hibernate generating? That's an error from the planner.
It does sound like you're trying to query back more than
Tom Lane wrote:
=?UTF-8?Q?Bj=C3=B8rn?= T Johansen [EMAIL PROTECTED] writes:
What does this mean and how can it be fixed?
Reduce the number of columns in your SELECTs?
This whiffs to me of excruciatingly bad schema design. How could you
possibly need upwards of a thousand columns in a
On Wed, 02 Jul 2008 03:04:04 -0400
Tom Lane [EMAIL PROTECTED] wrote:
=?UTF-8?Q?Bj=C3=B8rn?= T Johansen [EMAIL PROTECTED] writes:
What does this mean and how can it be fixed?
Reduce the number of columns in your SELECTs?
This whiffs to me of excruciatingly bad schema design. How could
Hi,
We have an IBM System x3850 machine running on RHEL 4.5 Cluster Suite
with high-availability enabled. During a huge delete process, PostgreSQL
(8.3.1) exhausts available memory and receives an OOM kill.
$ /srv/usr/bin/psql -e -f
What should I replace the command
INSERT INTO table (name) VALUES (value) RETURNING currval('my_id_seq')
into my_var;
with if I have to use version 8.1?
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
am Wed, dem 02.07.2008, um 11:58:19 +0200 mailte A B folgendes:
What should I replace the command
INSERT INTO table (name) VALUES (value) RETURNING currval('my_id_seq')
into my_var;
with if I have to use version 8.1?
select currval('my_id_seq');
Andreas
--
Andreas Kretschmer
Kontakt:
On Wed, 02 Jul 2008 15:24:38 +0800
Craig Ringer [EMAIL PROTECTED] wrote:
Tom Lane wrote:
=?UTF-8?Q?Bj=C3=B8rn?= T Johansen [EMAIL PROTECTED] writes:
What does this mean and how can it be fixed?
Reduce the number of columns in your SELECTs?
This whiffs to me of excruciatingly bad
Can anyone recommend a good tool for building simple web forms w/ a
PostgreSQL backend? Emphasis on simple - single table contact info
forms, etc. Something that can be presented to end users w/out a lot of
hand-holding. E.g. I want a form w/ last name, first name, # of
guests, arrival date.
http://www.sqlmaestro.com/products/postgresql/
I've used the PHP Code Generator with great success for simple stuff
like you describe. You could then write a function to do email
notifications or whatever you want.
Jon
-Original Message-
From: [EMAIL PROTECTED]
Roberts, Jon [EMAIL PROTECTED] writes:
Version: PostgreSQL 8.3.0, compiled by Visual C++ build 1400
Well, there are plenty of known bugs in 8.3.0 by now. You really
should update before complaining, not after.
I'm not complaining. I just want to make sure that if I upgrade, it
will fix
Tom Lane wrote:
Roberts, Jon [EMAIL PROTECTED] writes:
Version: PostgreSQL 8.3.0, compiled by Visual C++ build 1400
Well, there are plenty of known bugs in 8.3.0 by now. You really
should update before complaining, not after.
Yes. And the traditional question should be asked - is
Magnus Hagander [EMAIL PROTECTED] writes:
Tom Lane wrote:
But the syslogger process (and maybe others) is *not* supposed to
die.
Right. But are you saying we actually want to start up a new backend
in
a directory where we already have a running syslogger (and maybe
others)
processes,
Roberts, Jon wrote:
Roberts, Jon [EMAIL PROTECTED] writes:
Version: PostgreSQL 8.3.0, compiled by Visual C++ build 1400
Well, there are plenty of known bugs in 8.3.0 by now. You really
should update before complaining, not after.
I'm not complaining. I just want to make sure that if I
Roberts, Jon wrote:
Tom Lane wrote:
Roberts, Jon [EMAIL PROTECTED] writes:
Version: PostgreSQL 8.3.0, compiled by Visual C++ build 1400
Well, there are plenty of known bugs in 8.3.0 by now. You really
should update before complaining, not after.
Yes. And the traditional question should be
Roberts, Jon wrote:
Tom Lane wrote:
Roberts, Jon [EMAIL PROTECTED] writes:
Version: PostgreSQL 8.3.0, compiled by Visual C++ build 1400
Well, there are plenty of known bugs in 8.3.0 by now. You really
should update before complaining, not after.
Yes. And the traditional question
On Tue, Jul 1, 2008 at 5:52 PM, Albe Laurenz [EMAIL PROTECTED] wrote:
If you don't need SSL, set 'ssl=off' in postgresql.conf.
If you want SSL,
1) read the manual on SSL support
http://www.postgresql.org/docs/8.3/static/ssl-tcp.html
2) Is there a file server.key? If yes, make it readable to
Dave Coventry wrote:
If you want SSL,
2) Is there a file server.key? If yes, make it readable to the
postgres user. If not, create it as documented.
Here is the contents of my /var/lib/postgresql/8.2/main/ :
[EMAIL PROTECTED]:/var/lib/postgresql/8.2/main# ls -l
total 9
drwx-- 7
Roberts, Jon wrote:
Roberts, Jon wrote:
Tom Lane wrote:
Roberts, Jon [EMAIL PROTECTED] writes:
Version: PostgreSQL 8.3.0, compiled by Visual C++ build 1400
Well, there are plenty of known bugs in 8.3.0 by now. You really
should update before complaining, not after.
Yes. And the traditional
El mié, 02-07-2008 a las 08:02 +0200, Martijn van Oosterhout escribió:
On Tue, Jul 01, 2008 at 10:02:39AM -0500, Felipe de Jesús Molina Bravo wrote:
Hi
what can i do for a SRF written in C, can called as follow:
select * from obtAscendencia('(11099,15685)','(6808,9621)');
I
I am interesting in finding a good Postgres benchmark. I an not
interested in seeing how fast Postgres is compared to MySql, Firebird,
or any other SQL database.
What I am interested in is how file systems, memory, and X-64 vs X-32
effects the performance of Postgres.
It is more for my own
David Siebert wrote:
I am interesting in finding a good Postgres benchmark. I an not
interested in seeing how fast Postgres is compared to MySql, Firebird,
or any other SQL database.
What I am interested in is how file systems, memory, and X-64 vs X-32
effects the performance of Postgres.
It is
Felipe de Jesús Molina Bravo wrote:
I suspect that my error is:
r = obtPadre( intF-izq, intF-der );
You didn't show obtPadre().
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
--
Not having looked at the internals of db_link, I'd say it's certainly
possible that this is the reason for the failed restart. If db_link is
blocking something, the postmaster can't kill it off, and it'll still
be
sitting there holding a reference to the shared memory segment.
That said,
Roberts, Jon wrote:
Not having looked at the internals of db_link, I'd say it's certainly
possible that this is the reason for the failed restart. If db_link is
blocking something, the postmaster can't kill it off, and it'll still
be
sitting there holding a reference to the shared memory
Volkan YAZICI [EMAIL PROTECTED] writes:
We have an IBM System x3850 machine running on RHEL 4.5 Cluster Suite
with high-availability enabled. During a huge delete process, PostgreSQL
(8.3.1) exhausts available memory and receives an OOM kill.
Are there any foreign keys referencing this table?
Craig Ringer wrote:
David Siebert wrote:
I am interesting in finding a good Postgres benchmark. I an not
interested in seeing how fast Postgres is compared to MySql, Firebird,
or any other SQL database.
What I am interested in is how file systems, memory, and X-64 vs X-32
effects the
Well that is the rub. I am currently using Postgres everyday. It runs
like a champ and even on an old PIII 600 MHZ machine with a single old
and slow IDE drive and 256 megs of ram it is fast enough for what we do.
This is more for me to do some testing with.
I think it would useful as a tunning
Roberts, Jon [EMAIL PROTECTED] writes:
I'm not complaining. I just want to make sure that if I upgrade, it
will fix the problem. An upgrade could possible introduce a new
problem. I also wonder if this is isolated to Win32 because we are
upgrading to Solaris very soon.
The specific problem
El mié, 02-07-2008 a las 10:39 -0400, Alvaro Herrera escribió:
Felipe de Jesús Molina Bravo wrote:
I suspect that my error is:
r = obtPadre( intF-izq, intF-der );
You didn't show obtPadre().
ok it is:
Racional* obtPadre( Racional *li, Racional *ld){
BTW, just looking at win32_shmem.c ...
retptr = malloc(bufsize + 1 + 18);/* 1 NULL and 18 for
* Global\PostgreSQL: */
if (retptr == NULL)
elog(FATAL, could not allocate memory for shared memory name);
strcpy(retptr,
Klint Gore [EMAIL PROTECTED] writes:
Can someone shed some light on what's happening here?
D:\backupspg_dump -Z 9 -Fc -C -U postgres -f sheepcrc\dbback.dmp sheepcrc2
pg_dump: Dumping the contents of table uploadeddatafiles failed:
PQgetCopyData
() failed.
pg_dump: Error message from server:
Magnus Hagander [EMAIL PROTECTED] writes:
Not likely, but I'd test it anyway. If the issue is related to AV, it's
certainly fine - you won't be running AV on your Solaris. But more
importantly, Unix has actual support for signals and not just the fake
stuff we have on Win32, so it's likely
Tom Lane wrote:
Magnus Hagander [EMAIL PROTECTED] writes:
Not likely, but I'd test it anyway. If the issue is related to AV, it's
certainly fine - you won't be running AV on your Solaris. But more
importantly, Unix has actual support for signals and not just the fake
stuff we have on Win32,
Magnus Hagander [EMAIL PROTECTED] writes:
I'll see if I can repro a case like it to see if the syslogger prevents
the shared mem from going away when I get back to a dev box. Should be
enough to just stick a sleep preventing it from stopping, right?
The syslogger isn't restarted at all during
Hello,
Is it possible to use a join keyword in a delete?
For example:
DELETE FROM data_table1
using data_table2 INNER JOIN
data_table1 ON data_table1.fkey = data_table2.pkey;
It is not directly mentioned in the delete syntax but the delete refers
On Wed, Jul 2, 2008 at 8:35 AM, Roberts, Jon [EMAIL PROTECTED] wrote:
http://www.sqlmaestro.com/products/postgresql/
I've used the PHP Code Generator with great success for simple stuff
like you describe. You could then write a function to do email
notifications or whatever you want.
Jon
Bah. Must be pgAdmin, then. In its role creation dialogue, INHERIT is
definitely off by default. Guess that's not you guys, though. Sorry to have
impugned your judgement... =)
-cb.
Chandra Barnett [EMAIL PROTECTED] writes:
That did it! Thanks, all.
(Out of curiosity, what's the
--- On Wed, 7/2/08, Gwyneth Morrison [EMAIL PROTECTED] wrote:
From: Gwyneth Morrison [EMAIL PROTECTED]
Subject: [GENERAL] Delete from Join
To: pgsql-general@postgresql.org
Date: Wednesday, July 2, 2008, 3:15 PM
Hello,
Is it possible to use a join keyword in a delete?
For example:
Matt Magoffin [EMAIL PROTECTED] writes:
Below is a test case that simulates the use of xpath() within a plpgsql
function in my application.
I'm able to duplicate the memory leak in this function with the current
Fedora 8 libxml2 (2.6.32). The leak is definitely inside libxml2
itself, because
Text with the '/' character gets treated as a file path, e.g.
select * from to_tsvector('english', 'home/work');
gives only the single token:
'home/work':1
Changing '/' to '-' gives
'home':2 'work':3 'home-work':1
which is much more desirable for this application.
Is there an easy way to
Hallo,
I would to ask about function (vide subject) transcoding the characters
between different character pages on the fly: is it smart enough to skip
any transcoding operation, when both client and database are set to use
the same encoding already?
To make it more clear: I've got an
I looked through the libxml2 sources a little bit but couldn't
immediately find the problem. I'm fairly confident though that
this could be reproduced outside Postgres, by replicating the sequence
of libxml2 calls we make in xpath(). The next step should probably be
to build a reproducer
--- On Wed, 7/2/08, Gwyneth Morrison [EMAIL PROTECTED] wrote:
From: Gwyneth Morrison [EMAIL PROTECTED]
Subject: [GENERAL] Delete from Join
To: pgsql-general@postgresql.org
Date: Wednesday, July 2, 2008, 3:15 PM
Hello,
Is it possible to use a join keyword in a delete?
For
On Wed, 2 Jul 2008, Tom Lane wrote:
Matt Magoffin [EMAIL PROTECTED] writes:
Below is a test case that simulates the use of xpath() within a plpgsql
function in my application.
I'm able to duplicate the memory leak in this function with the current
Fedora 8 libxml2 (2.6.32). The leak is
I'm able to duplicate the memory leak in this function with the current
Fedora 8 libxml2 (2.6.32). The leak is definitely inside libxml2
itself, because the bloat shows up here:
I think this should fix it.
Kris Jurka
It looks like xml.c source has changed considerably since 8.3 (looking
Matt Magoffin [EMAIL PROTECTED] writes:
It looks like xml.c source has changed considerably since 8.3
No, hardly at all actually, but this patch happens to be right next door
to one of the lines that did change. cstring_to_text() replaces some
grottier stuff that used to be used for the same
I think this should fix it.
Kris Jurka
It looks like xml.c source has changed considerably since 8.3 (looking at
revision 1.68.2.2 from the 8.3.3. release). Do you know where/if this
patch would apply to the 8.3 branch?
I diff'ed 1.74 and 1.68.2.2, and I'm guessing this new line could be
Hello,
I try to use an old cluster into a new system.
The new system comes with a newer version of postgres so I uninstalled it
and I installed the same version that I had in the older system ---8.1
I got impressed when I Installed the 8.1 with dpkg -i and it started to run
without starting
Matt Magoffin [EMAIL PROTECTED] writes:
I think this should fix it.
Kris Jurka
Confirmed, that makes it go away nicely here:
LibxmlContext: 57344 total in 3 blocks; 55720 free (202 chunks); 1624 used
It looks like xml.c source has changed considerably since 8.3 (looking at
revision
Matt Magoffin [EMAIL PROTECTED] writes:
Later, I added a large set of plpgsql trigger functions that operate on
that new xml column data, using the xpath() function to extract bits of
XML and populate them into normal tables. The server has been running in
this fashion for many months now, and
John DeSoi [EMAIL PROTECTED] writes:
Is there an easy way to change '/' to be treated like '-' ? I've
looked over the documentation several times and could not find
anything. Even just a way to get the two tokens 'home' and 'work'
without the joined form would be helpful.
Seems like the
Take a look here, in the notes section:
http://www.postgresql.org/docs/8.3/interactive/sql-delete.html
on the using keyword.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Zbigniew Baniewski [EMAIL PROTECTED] writes:
I would to ask about function (vide subject) transcoding the characters
between different character pages on the fly: is it smart enough to skip
any transcoding operation, when both client and database are set to use
the same encoding already?
Yes.
Tom Lane wrote:
Klint Gore [EMAIL PROTECTED] writes:
Can someone shed some light on what's happening here?
D:\backupspg_dump -Z 9 -Fc -C -U postgres -f sheepcrc\dbback.dmp sheepcrc2
pg_dump: Dumping the contents of table uploadeddatafiles failed:
PQgetCopyData
() failed.
pg_dump: Error
Klint Gore [EMAIL PROTECTED] writes:
Tom Lane wrote:
Maybe it's
dying here after having leaked a lot of memory for some other reason
--- try watching the pg_dump process size while it runs.
Peak memory usage was about 540m which brought the total usage for the
machine to about half the
This part seems to match the bug though --- the leak is approximately
the same size as all the text returned by xpath() within the current
transaction.
So there may be a second issue remaining to be found. Can you put
together a test case for the long-term small leak?
Tom Lane wrote:
Klint Gore [EMAIL PROTECTED] writes:
Tom Lane wrote:
Maybe it's
dying here after having leaked a lot of memory for some other reason
--- try watching the pg_dump process size while it runs.
Peak memory usage was about 540m which brought the total usage for the
machine to
Hi All,
I am confused with the 'ident sameuser' authentication. Here's my
setup:
[EMAIL PROTECTED] ~]$ grep -v ^# data_dir/pg_hba.conf
local all all ident sameuser
hostall all 127.0.0.1/32 ident sameuser
hostall
On Wed, Jul 2, 2008 at 9:55 PM, Gurjeet Singh [EMAIL PROTECTED] wrote:
As you can see, if I use the machine's interface or unix sockets, it either
asks for password or lets me in. But when I use localhost, it correctly uses
127.0 line for authentication, but does not let me in!!!
Is this
On Sun, 2008-06-29 at 17:58 +0200, Magnus Hagander wrote:
This is not something you currently can do. We can only do LDAP
authentication, not authorization. There's no way to restrict it to a
particular group.
We're very interested in this functionality (nss_ldap for PgSQL) -- so
if there's a
Hi all.
I am using Postgres 8.3 with Windows XP Pro.
System date format is dd/MM/
Having problems when I writing records to a database with a single
'date' type field.
e.g. FieldByName('Date').ASString:='2/2/2003'
When the row is viewed in pgAdmin it is always 1899-12-30
I have tried
Matt Magoffin [EMAIL PROTECTED] writes:
So there may be a second issue remaining to be found. Can you put
together a test case for the long-term small leak?
Hmm, I'm not sure what else to add to this test case. This test case was a
good example of what our database is doing with xpath(); it
Klint Gore [EMAIL PROTECTED] writes:
Tom Lane wrote:
Maybe you've found a memory leak in pg_dump (it wouldn't be the first
one). Does this database have a particularly large number of objects?
I wouldn't call it large - 27 tables, 111 functions, 21 custom types
(used for set returning
Tom Lane wrote:
Klint Gore [EMAIL PROTECTED] writes:
Tom Lane wrote:
Maybe you've found a memory leak in pg_dump (it wouldn't be the first
one). Does this database have a particularly large number of objects?
I wouldn't call it large - 27 tables, 111 functions, 21 custom types
(used for
Klint Gore [EMAIL PROTECTED] writes:
Tom Lane wrote:
Would you be willing to send me a pg_dump -s (ie, just schema no
data) dump of this DB? Off-list of course.
attached. created with pg_dump 8.3.3 win32 to the 8.3.1 win32 server.
Thanks. When I reload this here and try to pg_dump it, I
Probably the right thing for you to do now is just to install the known
fix, and keep an eye on your server for awhile to see if you still see
any indication of the long-term leak behavior.
Certainly, that is my plan. Once I can get the patch rolled out to these
systems, I should be able to
J Ottery wrote:
Hi all.
I am using Postgres 8.3 with Windows XP Pro.
System date format is dd/MM/
Having problems when I writing records to a database with a single
'date' type field.
e.g. FieldByName('Date').ASString:='2/2/2003'
What is delphi's ShortDateFormat set to?
Does
79 matches
Mail list logo
