-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/06/06 23:02, Joshua D. Drake wrote:
On Thursday 06 July 2006 19:55, Ron Johnson wrote:
Being an HP/Compaq shop, I'm looking at an Opteron-and-SATA-based
DL145 G2 and an MSA20 SATA enclosure with a U320 interface to use
with RHES4 and
binberati wrote:
Hi,
I have a strange problem running Django on a GrokThis.net shared
hosting account:
Environment:
--
Apache/2.0.59 (Unix)
mod_fastcgi/2.4.2
PostgreSQL 8.1.3
--
On 19 Oct 2006 02:49:23 -0700, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:3. The last question is, is there any debbuger to debugg triggers in
plpgsql? This could be very usefull.You can try EnterpriseDB, to test/debug your triggers, and then port it back to your 7.xx version (assuming you do not
Hi,
i migrated my database from postgres 7.3 to postgres
8.1.
I was wondering if there is a way to verify that data
has been well copied betweeen the 2 versions !
I thought about writing a script that will verify that
we have the same tables and the same number of lines
per table between the 2
I was performing a bunch of INSERTs into a table, users, that has a
unique index on username. During the transaction, my internet connection
dropped. The INSERTs were being done inside a transaction.
Once I had manhandled my DSL router back online, I went back into a
console to redo the
do a ps -ef | grep transact
and look for idle in transaction postmaster processes.
If you're certain that nobody else is running that transaction (i.e. nobody on
the system or the process with the idle transaction has been sitting there
for a while and normally the application doesn't have long
Its always said that don't kill -9 postmaster.
Whats the reason not to do it. Why is it so strictly prohibited?
Thanks,
~Harpreet.
Jas, you might need to check the uplink and downlink time of your network router.
Also,check the postgresql.conf file to see various timeouts there. Comment all the timeouts to set them to infinity so that your Unix tools server keeps trying connecting to the Postgres server.
Also, check if you
On 10/19/2006 10:13:46 PM, Tom Lane wrote:
Karl O. Pinc [EMAIL PROTECTED] writes:
I would expect that because a row exists, even
though the value assigned is NULL, FOUND would
be TRUE. Are my expectations wrong?
No, but I think your code is. Please provide a test case
demonstrating
this
Hello!
I run an [almost] OLTP system with PG as backend on Windows and on Linux.
The idea is obvious - increase performance as much as possible keeping
reliability in mind and I'd highly appreciate any hints.
Some questions about performance/reliability trade.
My first idea was to increase
Harpreet Dhaliwal writes:
Its always said that don't kill -9 postmaster.
Whats the reason not to do it. Why is it so strictly prohibited?
,[
http://www.postgresql.org/docs/8.1/static/postmaster-shutdown.html#AEN18182 ]
| It is best not to use SIGKILL to shut down the server. Doing so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/20/06 05:27, Andreas Seltenreich wrote:
Harpreet Dhaliwal writes:
Its always said that don't kill -9 postmaster.
Whats the reason not to do it. Why is it so strictly prohibited?
,[
Hi,
1. On Postgresql 8.1.4, i can't use pg_terminate_backend(int) function.
How can i use this function?
2. How can i execute a shell command?
I need to terminate a client connection(some times active, some times
idle one) by a query. I can undertake the risc for it. :)
Regards,
Mustafa
Ron Johnson writes:
On 10/20/06 05:27, Andreas Seltenreich wrote:
,[
http://www.postgresql.org/docs/8.1/static/postmaster-shutdown.html#AEN18182
]
| It is best not to use SIGKILL to shut down the server. Doing so will
| prevent the server from releasing shared memory and semaphores,
On Wed, Oct 18, 2006 at 04:43:40PM -0400, Ron Peterson wrote:
On Wed, Oct 18, 2006 at 04:31:57PM -0400, Ron Peterson wrote:
I'm having a hard time finding any examples of functions returning
timestamps I can study to see how they are handled internally. I'm sure
it's only a line or two
Hi,Ale Raza wrote:
Ok, it means I
can not use MS VC complier/linker, only choice is Mingw or Cygwin. I think you can use MS VC, you can try to find some info from here:
http://www.postgresql.org/docs/8.0/interactive/xfunc-c.htmlRead user comments at the bottom.Ale Raza wrote:
Wondering if
you
Am Freitag, 20. Oktober 2006 13:12 schrieb Ron Johnson:
But it can't be fatal, can it? After all, that's what a system
crash is, right?
Perhaps we should add another tip not to crash the system.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of
Andreas Seltenreich wrote:
Ron Johnson writes:
On 10/20/06 05:27, Andreas Seltenreich wrote:
,[
http://www.postgresql.org/docs/8.1/static/postmaster-shutdown.html#AEN18182 ]
| It is best not to use SIGKILL to shut down the server. Doing so will
| prevent the server from releasing shared
Shane Ambler wrote:
The one thing worse than kill -9 the postmaster is pulling the power
cord out of the server. Which is what makes UPS's so good.
If your server is changing the data file on disk and you pull the power
cord, what chance do you expect of reading that data file again?
1.
Ron Peterson writes:
On Wed, Oct 18, 2006 at 04:43:40PM -0400, Ron Peterson wrote:
I'm pretty close, but I'm still not understanding something about
PostgreSQL's internal timestamp representation. If I do 'select
now();', I get a return value with microsecond resolution, which would
seem to
If your server is changing the data file on disk and you pull the power
cord, what chance do you expect of reading that data file again?1.That's what we have WAL for.The only thing that can really killyou is the use of non-battery-backed write cache.
Just for information: I had to suffer
On Fri, Oct 20, 2006 at 10:56:09PM +0930, Shane Ambler wrote:
Someone in the thread mentioned having to clean up shared mem. I've had
to do this often with oracle:
root# ipcs
-- Shared Memory Segments
keyshmid owner perms bytes nattch status
Bernard Grosperrin wrote:
Oisin
SELECT location_id, (sold_parts_amount_dly + sold_labor_amount_dly) /
(sold_parts_amount_dly + sold_labor_amount_dly) from sales where
(sold_parts_amount_dly + sold_labor_amount_dly)0
Thanks for your answer.
The real request would be something like this:
Alvaro Herrera [EMAIL PROTECTED] writes:
Shane Ambler wrote:
The one thing worse than kill -9 the postmaster is pulling the power
cord out of the server. Which is what makes UPS's so good.
If your server is changing the data file on disk and you pull the power
cord, what chance do you
On Fri, Oct 20, 2006 at 03:32:05PM +0200, Andreas Seltenreich wrote:
Ron Peterson writes:
On Wed, Oct 18, 2006 at 04:43:40PM -0400, Ron Peterson wrote:
I'm pretty close, but I'm still not understanding something about
PostgreSQL's internal timestamp representation. If I do 'select
On 10/20/06, Shane Ambler [EMAIL PROTECTED] wrote:
After all, that's what a system crash is, right? A system crash is safer in that it won't leave orphaned child
processes or IPC/synchronization resources around, making it more comparable to a SIGQUIT than a SIGKILL.The one thing worse than kill
Dawid Kuroczko wrote:
On 10/20/06, Shane Ambler [EMAIL PROTECTED] wrote:
The one thing worse than kill -9 the postmaster is pulling the power
cord out of the server. Which is what makes UPS's so good.
Well, I think that pulling the power cord is much safer than killing -9
the postmaster.
Hello,I have a table like this:create table dummy (value integer primary key);and I insert a row like thisinsert into dummy values(0);then I want to insert three rows:insert into dummy values(0);insert into dummy values(1);insert into dummy values(2);none of them will be inserted because the first
We're looking to upgrade from 7.4 - should we go to 8.1.5 or 8.2?
We have two databases; 7.4.6 and 7.4.11 in a master slave config using
Slony. Both databases use the C locale with UTF-8 encoding on unix.
We've dumped and loaded the data into an 8.1.4 database and have seen no
problems with
Shane Ambler wrote:
Dawid Kuroczko wrote:
On 10/20/06, Shane Ambler [EMAIL PROTECTED] wrote:
The one thing worse than kill -9 the postmaster is pulling the power
cord out of the server. Which is what makes UPS's so good.
Well, I think that pulling the power cord is much safer than
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/20/06 10:09, John Sidney-Woollett wrote:
We're looking to upgrade from 7.4 - should we go to 8.1.5 or 8.2?
We have two databases; 7.4.6 and 7.4.11 in a master slave config using
Slony. Both databases use the C locale with UTF-8 encoding on
On Sat, Oct 21, 2006 at 12:20:35AM +0930, Shane Ambler wrote:
If you kill -9 the postmaster the system can still finish sending
changes to disk and close the file but pulling the power cord can stop a
write in the middle of a block giving you half new data and half old
data in the one file.
John Sidney-Woollett [EMAIL PROTECTED] writes:
Are the differences between 8.1.5 and 8.2 significant? Is 8.2 more about
speed or new features?
8.2 is still all about beta testing.
regards, tom lane
---(end of
Martijn van Oosterhout kleptog@svana.org writes:
Well, if you kill -9 the postmaster all the connections stay alive and
stay processing tuples and writing to disk, except the coordination is
gone.
The postmaster isn't involved in any critical inter-backend coordination.
If you kill -9 the
On 10/20/06, Jean-Christophe Roux [EMAIL PROTECTED] wrote:
Hello,
I have a table like this:
create table dummy (value integer primary key);
and I insert a row like this
insert into dummy values(0);
then I want to insert three rows:
insert into dummy values(0);
insert into dummy values(1);
insert
No I cannot risk live data...
But I (think I) read that 8.2 was expected to go final in November/December.
So my question was is it worth waiting for 8.2 final or to go with 8.1.5
now. I guess going with 8.1.5 is what we should do.
Thanks
John
Ron Johnson wrote:
-BEGIN PGP SIGNED
Is there a page that describes the new features/improvements between
8.1.5 and 8.2? I couldn't find one on the postgres website.
If there aren't *big* performance gains between 8.1.5 and 8.2 then we'll
go with 8.1.5 and leave the 8.2 upgrade till sometime next summer.
John
Tom Lane wrote:
John,No I cannot risk live data...please read closely: Ron wrot Can you risk your app on beta software? ..
There is allways a risk included in basing an application on beta software, as programming interfaces may change.BUT:My experience is: you can trust your data to PostgreSQL. The elephant
Thanks for the link - that was very useful.
John
Alvaro Herrera wrote:
John Sidney-Woollett wrote:
Is there a page that describes the new features/improvements between
8.1.5 and 8.2? I couldn't find one on the postgres website.
If there aren't *big* performance gains between 8.1.5 and 8.2
After all that discussion that took place while i was sleeping, I have a few more questions simply haunting me.Someitmes, rather most of the times, when I start postgres using pg_ctl, it says antoher postmaster is running. Being a total naive about the hazzards of kill -9 postmaster, i simply used
Rick Gigger [EMAIL PROTECTED] writes:
To make a long story short lets just say that I had a bit of a
hardware failure recently.
If I got an error like this when trying to dump a db from the mangled
data directory is it safe to say it's totally hosed or is there some
chance of recovery?
On Fri, 2006-10-20 at 16:09 +0100, John Sidney-Woollett wrote:
We're looking to upgrade from 7.4 - should we go to 8.1.5 or 8.2?
I think the biggest question is whether your deployment can wait for the
stable release of 8.2, including possible delays.
Also, of course, check out the release
From what I've seen 8.2 is going to offer several nice new features, but
I would move to 8.1.5 for now.
Honestly, I would probably wait until 8.2.1 is available before moving
to that subversion. No offense against the PG team, but I've been
burned by zeroes once too many times to go live with
I was looking through the various contrib packages and pgfoundry
projects. I noticed that many of them are GPL like PostGIS or LGPL
like Npgsql. I have questions.
If you make create a PostgreSQL database that uses PostGIS and you
distribute that database, than your database (tables, stored
On 10/20/06, John Sidney-Woollett [EMAIL PROTECTED] wrote:
We're looking to upgrade from 7.4 - should we go to 8.1.5 or 8.2?
We have two databases; 7.4.6 and 7.4.11 in a master slave config using
Slony. Both databases use the C locale with UTF-8 encoding on unix.
We've dumped and loaded the
Hi all,
for further investigation we seperated the sub-SELECT from the DELETE
statement and it looks like the SELECT is usually finished in some 100
milliseconds but after some minutes it suddenly takes some minutes.
Peter
2006/10/20, Peter Bauer [EMAIL PROTECTED]:
Hi all,
we have a theory
Karen Hill wrote:
I was looking through the various contrib packages and pgfoundry
projects. I noticed that many of them are GPL like PostGIS or LGPL
like Npgsql. I have questions.
If you make create a PostgreSQL database that uses PostGIS and you
distribute that database, than your
Karen Hill wrote:
If you make create a PostgreSQL database that uses PostGIS and you
distribute that database, than your database (tables, stored
procedures, views, etc) are GPL?
Nothing ever becomes GPL automatically. You may wish to distribute your
own work under the GPL, but you don't
Karen Hill wrote:
John Hasler wrote:
Npgsql is LGPL. It means you must release the source of Npgsql when
distributing it, and if you modify Npgsql, but not have to release the
source under the (L)GPL of the software that calls Npgsql functions?
Pretty much, but you must provide your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/20/06 13:49, Joshua D. Drake wrote:
Karen Hill wrote:
I was looking through the various contrib packages and pgfoundry
projects. I noticed that many of them are GPL like PostGIS or LGPL
like Npgsql. I have questions.
If you make create
On Fri, Oct 20, 2006 at 03:35:34PM -0500, Ron Johnson wrote:
Exactly. The Linus View is that dynamic linking and socket
conversations are *not* linking in the GPL2 meaning, but the FSF
RMS think differently. The GPL3 seems to codify that strictness.
Dynamic linking may be an issue, but
Thanks for the info. I think that we'll move to 8.1.5 first, and then
8.2 when it's stable. We have to keep our test and production systems in
sync (version-wise).
John
Merlin Moncure wrote:
I've been developing against 8.2 for months without a single 8.2
specific problem. I run both linux
Hi,
Does anybody know what's the meaning of the c (lowercase) privilege in
PostgreSQL 8.2 Beta?
bd_test=# SELECT datacl FROM pg_catalog.pg_database WHERE datname='bd_test';
datacl
--
{=CTc/user1,user1=CTc/user1}
On Fri, 20 Oct 2006, Javier Carlos wrote:
Does anybody know what's the meaning of the c (lowercase) privilege in
PostgreSQL 8.2 Beta?
That should be for CONNECT privilege.
---(end of broadcast)---
TIP 6: explain analyze is your friend
Hello
A newbie to PostgreSQL from MySQL and just trying to learn tsearch2. In
one of the examples at:
http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/docs/tsearch-V2-intro.html
the query given is:
SELECT intindex, strTopic FROM tblmessages
WHERE idxfti @@
Hello,
I'm concerned about whether the usual parameter escaping mechanism is enough in
a LIKE or regular expression search.
I run a recent Postgres version and use the Python connector psycopg2 for a web
application. I understand that if I always escape as in
dBres=dBcsr.execute('SELECT
Hi all,
we have a theory for the root of all evil which causes a reproducable
deadlock which is not detected by Postgre:
The DELETE statement contains a select which waits for a sharelock
(according to pg_locks and pg_stat_activity) on rows locked by the
UPDATE statement. The UPDATE itself
On 10/20/06, Tom Lane [EMAIL PROTECTED] wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Shane Ambler wrote:
The one thing worse than kill -9 the postmaster is pulling the power
cord out of the server. Which is what makes UPS's so good.
If your server is changing the data file on disk and
The following encoding behavior seems strange to me (v8.1.4). I have
read the docs, but I am still confused.
I have a UTF8 encoded database. I can do
= SELECT '\xb9'::text;
But that seems to be the only way to get an invalid utf8 byte sequence
into a text type.
Even if I do PQexecParams and
On 2006-10-20, Karen Hill [EMAIL PROTECTED] wrote:
If you make create a PostgreSQL database that uses PostGIS and you
distribute that database, than your database (tables, stored
procedures, views, etc) are GPL?
No, because those tables, stored procedures etc. are not
derivative works of the
Merijn de Weerd wrote:
[...]
If you distribute the PostgreSQL server software linked with
the PostGIS software, then you have to comply with the GPL
for both parts of that derivative work.
If you don't distribute any server software, you do not have
to worry about what the GPL requires.
I got the following error (v8.1.4):
PANIC: ERRORDATA_STACK_SIZE exceeded
There was a discussion about this same error on the list 3 days ago.
However, it looks like I'm having a different problem.
I have an ON INSERT rule that executes 3 functions similar to the
following function:
CREATE OR
Ritesh --
You are correct in thinking that @@ is a special operator defined for
tesearch2; it uses the GIST indexes to do a search, but more than that I can't
say, since I am not really familiar with tsearch2. (In the postGIS world there
is a vaguely equivalent operator, , again using
Hi,
This should be a relatively simple question... I just made a custom type
in C, which I will use to build an array in one of my tables. I defined
an equality function in C, and declared an operator = on my custom type
that calls my equality operator.
Along the lines of:
CREATE OPERATOR = (
Javier Carlos wrote:
Hi,
Does anybody know what's the meaning of the c (lowercase) privilege in
PostgreSQL 8.2 Beta?
connect
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
---(end
Morgan Kita [EMAIL PROTECTED] writes:
This should be a relatively simple question... I just made a custom type
in C, which I will use to build an array in one of my tables. ...
However, should array_eq be called for unique constraints? What am I
missing here to get this system working?
It is just me, or is everyone getting duplicated old emails from a couple of
day ago?
Regards,
Richard Broersma Jr.
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to
Peter Bauer [EMAIL PROTECTED] writes:
we have a theory for the root of all evil which causes a reproducable
deadlock which is not detected by Postgre:
The DELETE statement contains a select which waits for a sharelock
(according to pg_locks and pg_stat_activity) on rows locked by the
UPDATE
Ian Harding [EMAIL PROTECTED] writes:
On 10/20/06, Tom Lane [EMAIL PROTECTED] wrote:
Personally I think the TIP that's really needed is never remove
postmaster.pid by hand.
When the machine crashes, don't you have to remove the pid file by
hand to get the Postgres to start? I seem to
I've seeing a few ... one just now dated 10/17 on conversion and Oracle ...
G
-Original Message-
From: [EMAIL PROTECTED] on behalf of Richard Broersma Jr
Sent: Fri 10/20/2006 8:43 PM
To: General PostgreSQL List
Cc:
Subject:[GENERAL] old duplicate emails
It is just
I would eventually like to:
1) find a way to (stress) test a mockup database server.
2) fix a near-realtime replication of our production database server
for pulling out statistics and reports. Minor bugs would be
permitable in such a setup. We don't need a full-fledged data
71 matches
Mail list logo
