During a maintenance window, we upgraded our systems to Postgres 9.0.13
from 9.0.3 running on FreeBSD 8.1 amd64.
When we restarted the postgres server, I notices, and continue to
notice, a recurrence of messages in the log.
2013-09-16 21:15:58 MDT LOG: automatic vacuum of table
"ishield.publi
: Benjamin Krajmalnik; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Installing multiple instances of Postgred on one FreeBSD
server
I used to do the ezjail route before but for ease, you can modify the setting
"unix_socket_directory" on your postgresql.conf and have it point to anoth
So essentially we would have to run jails on this - does that affect
performance?
-Original Message-
From: Jim Mercer [mailto:j...@reptiles.org]
Sent: Wednesday, May 01, 2013 2:20 PM
To: Benjamin Krajmalnik
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Installing multiple
: Benjamin Krajmalnik
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Installing multiple instances of Postgred on one
FreeBSD server
On Wed, May 01, 2013 at 01:58:21PM -0600, Benjamin Krajmalnik wrote:
> I need to migrate a production database from Postgres 9.0 to Postgres
> 9.2.
>
> Run
I need to migrate a production database from Postgres 9.0 to Postgres
9.2.
Running FreeBSD 8.1/amd64, and presently running Postgres 9.0.4.
Due to the nature of the application, I cannot have any considerable
downtime, so the pg_dump and install new version route is not an option.
I would like t
I currently have 2 servers running PostgreSQL 9.0 under FreeBSD
configured with streaming replication.
DB1 is the primary server, and DB2 is the replicated server, which is
used for all of the read only queries.
I am having some hardware issues on DB1 which is affecting its
performance, resulting
: Kevin Grittner [mailto:kgri...@mail.com]
Sent: Tuesday, January 22, 2013 5:23 PM
To: Benjamin Krajmalnik; pgsql-admin@postgresql.org
Subject: RE: [ADMIN] Schema design question as it pertains to performance
Benjamin Krajmalnik wrote:
> Kevin Grittner wrote:
>> Benjamin Krajmalnik wrote:
&
previously), so it is just a matter of fine tuning right now.
-Original Message-
From: Kevin Grittner [mailto:kgri...@mail.com]
Sent: Tuesday, January 22, 2013 2:56 PM
To: Benjamin Krajmalnik; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Schema design question as it pertains to performance
This question pertains to PG 9.0.4 running on FreeBSD amd64. Was not
sure if it should go into the general list or the performance list, so
my apologies if I opted for the wrong list.
We currently have a db schema which contains many wide indices which
usually contain one column which is constan
thx
Sent from my Verizon Wireless 4G LTE smartphone
Kevin Grittner wrote:
Benjamin Krajmalnik wrote:
> It is ok if I am a little bit behind. What setting do
> I need to tweak to allow it to get further behind?
The relevant settings are described here:
http://www.postgresql.org/do
It is ok if I am a little bit behind. What setting do I need to tweak to allow
it to get further behind?
-Original Message-
From: Kevin Grittner [mailto:kgri...@mail.com]
Sent: Thursday, January 17, 2013 4:32 PM
To: Benjamin Krajmalnik; pgsql-admin@postgresql.org
Subject: Re: [ADMIN
I have 2 servers which are using streaming replication (pg 9.0.4).
The secondary server is there primarily as a disaster recovery server,
but we are also using it for reporting, so as not to place undue load on
the primary server.
As I review the logs on the secondary server, I frequently see the
, January 08, 2013 7:17 PM
To: Benjamin Krajmalnik
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] General queston on getting rid of unused WAL files
"Benjamin Krajmalnik" writes:
> Looking at pg_xlogs, I see that postgres is sequentially reusing all
> of the available WAL files,
Yesyerday I had an issue where Postgres could not write to a fsm file
and started creating WAL files until it filled up the disk space on the
partition where the WAL files were located and panicked. I moved the
WASL files to the data partition, restarted postgres, and after about an
hour everythin
, January 07, 2013 7:24 PM
To: Benjamin Krajmalnik
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Possible database corruption
On 01/08/2013 05:22 AM, Benjamin Krajmalnik wrote:
I have a situation where pg_xlog started growing until it filled
up the disk drive.
This should not ever
Restarting the postmaster recreated the missing fsm file.
Recovery completed and database is back up.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
stem is in
recovery mode
2013-01-07 20:51:54 GMT [local]FATAL: the database system is in
recovery mode
From: Benjamin Krajmalnik
Sent: Monday, January 07, 2013 2:31 PM
To: Benjamin Krajmalnik; pgsql-admin@postgresql.org
Subject: RE: [ADMIN] Possible database corruption - urgent
I forgot
ot;: No such file or directory
2013-01-07 01:49:12 GMT CONTEXT: writing block 1 of relation
base/16748/181979366_fsm
2013-01-07 01:49:12 GMT WARNING: could not write block 1 of
base/16748/181979366_fsm
From: pgsql-admin-ow...@postgresql.org
[mailto:pgsql-admin-ow...@postgresql.org] O
I have a situation where pg_xlog started growing until it filled up the
disk drive.
I got alerted to the error and started investigating.
Checked the logs and I am seeing the following entry repeatedly:
2013-01-07 01:49:12 GMT ERROR: could not open file
"base/16748/181979366_fsm": No such fi
I am experiencing a little higher CPU load than I would like to see, and
was wondering if it has to do with the number of connections (although
many are idle).
I am running PG 9.0.4/amd64 on FreeBSD 8.1., dual boxes running
streaming replication.
Hardware is a 16 core box with 96GB RAM, using 6GB
In the documentation, it states we need to drop and recreate the
information schema.
A simple drop did not work (it required drop/cascade).
Executed the information_schema.sql. I see an entry (when using pgAdmin)
for the information_schema under the Catalogs, but I do not see any
catalog objects.
If I have never used pg_upgrade, so I believe I do not need to do
anything, correct?
> -Original Message-
> From: Kevin Grittner [mailto:kevin.gritt...@wicourts.gov]
> Sent: Wednesday, January 18, 2012 3:28 PM
> To: pgsql-admin; Benjamin Krajmalnik
> Subject: Re: [ADMIN]
I will be taking down all of our infrastructure to update firmware on
the controllers due to a bug affecting BBU (wonderful J ).
I was thinking of taking the opportunity and upgrading pg from 9.0.3
(amd64 on Freebsd 8.1) to the latest version 9.0.6.
In the release notes for 9.0.6, it mentions:
assistance, and I guess this pgstat
timeout can be attributed to the controller :)
> -Original Message-
> From: pgsql-admin-ow...@postgresql.org [mailto:pgsql-admin-
> ow...@postgresql.org] On Behalf Of Benjamin Krajmalnik
> Sent: Wednesday, January 04, 2012 11:48 AM
> T
while it is running,
and, of course, the exact command so I don't foobar things up.
> -Original Message-
> From: Kevin Grittner [mailto:kevin.gritt...@wicourts.gov]
> Sent: Wednesday, January 04, 2012 11:44 AM
> To: pgsql-admin; Benjamin Krajmalnik
> Subject: Re:
I have proceeded to do some more checking, and I see in iostat that the pg_xlog
drive has a significantly higher busy state than before. Whereas it was barely
busy when we first spun up the server (total %busy since we started the server
is about 6%) it is now in its 80's almost steady state.
Just a WAG - is it possible this is being caused by the connection
pooler (pgbouncer in my case)?
> -Original Message-
> From: pgsql-admin-ow...@postgresql.org [mailto:pgsql-admin-
> ow...@postgresql.org] On Behalf Of Benjamin Krajmalnik
> Sent: Thursday, December 22, 2011 1
the insertion of the
data, in which records are inserted and deleted - never updated.
> -Original Message-
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> Sent: Thursday, December 22, 2011 11:45 AM
> To: Benjamin Krajmalnik
> Cc: pgsql-admin
> Subject: Re: [ADMIN] Proble
Original Message-
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> Sent: Thursday, December 22, 2011 10:55 AM
> To: Benjamin Krajmalnik
> Cc: pgsql-admin
> Subject: Re: [ADMIN] Problem with pgstat timneouts
>
> "Benjamin Krajmalnik" writes:
> > About a month
About a month ago, I started receiving quite a few pgstat timeouts on my
production database.
PostgreSQL 9.0.3 on amd64-portbld-freebsd8.1, compiled by GCC cc (GCC)
4.2.1 20070719 [FreeBSD], 64-bit
I am not sure where to start looking for the cause.
Database has been up since march without any
Further to Scott's comment, we are running our application platform on
nginx/php (using php-fpm).
It scales very well and it is extremely fast.
When running under Apache, we had to constantly restart the apache
service because it could not handle the load (at 150 concurrent users
hitting the app it
You can check the running processes and grep aotovacuum.
You should see a launcher process which is always running.
If you use pgAdmin you can also look at the table statistics from the
GUI and see when was the last time autovacuum or autoanalyze ran on each
table.
From: pgsql-admin-ow...@
Has anyone heard from the Japanese members of the community?
I hope they are all well - our prayers are with them.
Keith,
there are 2 excellent books. I purchased them a few weeks ago as I was
about to migrate all of my infrastructure to new hardware, and they have
been invaluable. Simon, Hannu, and Greg did an awesome job.
I ordered some massive servers, and in the course of benchmarking them
following the
I have pgbouncer running on the same server, and I get over 2000 calls
to a php page per minute.
Each call does inserts data digests into partitioned tables.
I also have a multi-threaded daemon connected to the same database
running background operations on the data coming in.
Works flawlessly.
What may be happening is that it does not have enough time to run based
on your autovacuum settings.
Check your setting for autovacuum_vacuum_cost_limit. I believe default
is 200 - max is 1 which is what I have mine set to due to very heavy
table utilization.
> -Original Message-
> Fr
dropped.
> -Original Message-
> From: Scott Marlowe [mailto:scott.marl...@gmail.com]
> Sent: Monday, July 26, 2010 3:39 PM
> To: Benjamin Krajmalnik
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] upper and UTF-8
>
> I'd try creating a db with en_US or ev
CREATE DATABASE ishield
WITH OWNER = postgres
ENCODING = 'UTF8'
LC_COLLATE = 'C'
LC_CTYPE = 'C'
CONNECTION LIMIT = -1;
> -Original Message-
> From: Scott Marlowe [mailto:scott.marl...@gmail.com]
> Sent: Monday, July 26,
I just used the upper(text) function on a database which is utf8 encoded
and which has spanish text.
All of the regular characters were properly converted, except for
characters which had accents.
System is running PG 8.4.0 (I have been unable to upgrade because the
system needs to be up 24x7), FreeBSD 7.2 amd64, 8 cores, 16GB RAM.
Our application is a network monitoring system, so we are constantly
inserting vast amounts of data (server presently processes about 50
million transactions per
ssage-
> From: Alvaro Herrera [mailto:alvhe...@commandprompt.com]
> Sent: Monday, May 03, 2010 7:48 AM
> To: Benjamin Krajmalnik
> Cc: Tom Lane; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Autovacuum stopped running
>
> Benjamin Krajmalnik wrote:
> > OK.
> &
Tom,
1. I had to restart the postgres server, otherwise I would have been in
deep problems.
2. I just tried installing strace from the ports system - unfortunately
it appears that FreeBSD only has it for i38s, not amd64. Any
alternatives so that if this happens again I can take care of this?
>
OK.
This happened again on another server with these same settings.
I did not see any long running transaction, and the autovacuum launch
process was running.
> -Original Message-
> From: Benjamin Krajmalnik
> Sent: Saturday, May 01, 2010 5:22 PM
> To: 'Tom Lane'
t; -Original Message-
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> Sent: Saturday, May 01, 2010 5:10 PM
> To: Benjamin Krajmalnik
> Cc: Kevin Grittner; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Autovacuum stopped running
>
> "Benjamin Krajmalnik" w
for :) Thx.
> -Original Message-
> From: Kevin Grittner [mailto:kevin.gritt...@wicourts.gov]
> Sent: Saturday, May 01, 2010 8:27 AM
> To: Benjamin Krajmalnik; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Autovacuum stopped running
>
> "Benjamin Krajmalnik
I had a very strange occurrence 2 days ago where autovacuum appears to
have stopped running.
I did not see any error messages in pg_log. The problem caused a file
which is usually around 50Mb but which gets updated extensively to grow
to 105GB, which in turn brought the server's performance down
We recently added a text field to a table, and ended up dropping it and
moving it to a separate related table for performance reasons.
Previously, the toast table size was negligible, but now it is over
250MB.
I have tried performing a vacuum full against the table (this is an
inherited table), b
You are always very helpful.
> -Original Message-
> From: Scott Marlowe [mailto:scott.marl...@gmail.com]
> Sent: Wednesday, January 13, 2010 5:58 PM
> To: Benjamin Krajmalnik
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Question on moving data to new partit
I have some tables which have an extremely high amount of update
activity on them. I have changed autovacuum parameters (cost delay and
limit), and whereas before they would never be vacuumed and bloat they
are running fine.
However, as the platform scales, I am afraid I will reach the same
situa
Alvaro, Scott - thanks for your replies and the direction you pointed me
into.
The underlying problem was that the cost limit was too low, so the
autovacuum process would run forever and not be able to do anything. I
reduced the cost delay and increased the cost limit form the default of
200 to 1
0 8:40 PM
> To: Scott Marlowe
> Cc: Benjamin Krajmalnik; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Finetuning Autovacuum
>
> Scott Marlowe escribió:
> > On Mon, Jan 4, 2010 at 6:38 PM, Benjamin Krajmalnik
> wrote:
>
> > > Initially, I had scheduled tas
ows; 9832 rows in sample, 48155 estimated total rowsTotal query runtime:
6937 ms.
Any suggestions on how to better tune autovacuum, or alternatively do you
recommend just running a vacuum analyze as a pgagent scheduled task?
> -Original Message-
> From: Scott Marlowe [mailto:scott
PostgreSQL 8.4/FreeBSD 7.2 amd64
I have a database which has 3 tables which get a very high level of
activity (about 40 thousand updates per minute).
The tables are getting quite bloated, since autovacuum is apparently not
optimally configured (it is using the default settings).
Anything I d
Strange - seems to have sorted itself out.
I turned off a scheduled vacuum of the table and within a few minutes I
sorted itself out.
I have reduced the frequency of the vacuuming task which is being
carried out via pgagent.
From: Benjamin Krajmalnik
Sent: Monday, December 14, 2009 12:28
": moved 495
row versions, truncated 4479 to 4457 pages
DETAIL: CPU 0.00s/0.02u sec elapsed 0.02 sec.
INFO: index "pg_toast_145099_index" now contains 117973 row versions in
343 pages
DETAIL: 495 index row versions were removed.
0 index pages have been deleted, 0 are curre
I am trying to cluster a table for which vacuum full is not reducing its
size.
When I do so, I am getting the following error:
ERROR: missing chunk number 0 for toast value 207869115 in
pg_toast_145099
** Error **
ERROR: missing chunk number 0 for toast value 207869115
guidance.
As always, thank you so much for your assistance.
> -Original Message-
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> Sent: Tuesday, August 11, 2009 7:54 AM
> To: Benjamin Krajmalnik
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Max connecti
Yes, I had, but apparently the values were not high enough to
accommodate that many connections.
I retuned the IPC kernel setting, and now it appears to be running fine.
Thanks.
From: Shoaib Mir [mailto:shoaib...@gmail.com]
Sent: Monday, August 10, 2009 11:51 PM
To: Benjamin Krajmalnik
I am setting up a test environment to simulate a very high load. We
have a server farm which is receiving data (cold be thousands of
simultaneous users posting data). I currently have max_connections set
to 500 and the server is starting ok. If I try to increase the
max_connections to 1000, the
I recently built a test server running 8.4/FreeBSD 7.2/amd64, built from
the ports.
I am seeing the following message in the logs:
"autovacuum: found orphan table "pg_temp_1""."pga_tmp_zombies" in
database "postgres"
"autovacuum: found orphan table "pg_temp_2""."pga_tmp_zombies" in
databas
consider this closed unless I see it occur again.
Sorry for the false alarm.
> -Original Message-
> From: pgsql-admin-ow...@postgresql.org [mailto:pgsql-admin-
> ow...@postgresql.org] On Behalf Of Benjamin Krajmalnik
> Sent: Wednesday, July 29, 2009 5:00 PM
> To: Tom Lane
>
e worked around this by setting the variable to a blank string if
the value passed to the stored procedure is a null value, but there
definitely appears to be an issue in there.
> -Original Message-
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> Sent: Wednesday, July 29, 2009 4:43
e, timestamp
without time zone, integer, character varying, character varying,
integer) OWNER TO postgres;
> -Original Message-
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> Sent: Wednesday, July 29, 2009 3:31 PM
> To: Alvaro Herrera
> Cc: Benjamin Krajmalnik; pg
I tried it with both on and off, and it did not make a difference.
> -Original Message-
> From: Alvaro Herrera [mailto:alvhe...@commandprompt.com]
> Sent: Wednesday, July 29, 2009 3:20 PM
> To: Benjamin Krajmalnik
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN]
PostgreSQL 8.3.7 running on FreeBSD.
The following query:
update tblksalerts
set cleartime = x_cleartime,
laststatusid = x_statusid,
lastreplytext = x_replytxt,
lasttesttime = x_testtime
I apologize for the slightly off-topic question.
I will be building a new PostgreSQL server running 8.4 on FreeBSD 7.2
64-bit.
The nature of the application dictates that we use shared storage to
provide high availability (in case one of the servers has a failure).
After doing some research in t
I am running 8.3.7 on FreeBSD 7.0/amd64.
It appears that at some point about 2 weeks ago statistics tracking
ceased.
I have the following query which I use to track cache hits, and it is
not being updated:
SELECT pg_stat_database.datname, pg_stat_database.blks_read,
pg_stat_database.blks_hit,
Never mind.
I restarted PostgreSQL and stats are now collecting again.
From: Benjamin Krajmalnik
Sent: Friday, July 03, 2009 3:23 PM
To: pgsql-admin@postgresql.org
Subject: Statistical tracking issue
I am running 8.3.7 on FreeBSD 7.0/amd64.
It appears that at some point about 2 weeks
So what if he voices his beliefs.
This PC BS is over the top.
If you are so offended by his by-line, to the extent that you want to
remove yourself fomr the mailing lists, then by all means do so.
I am not a Christian (I am Jewish, so I guess that puts me one rung
below Bruce), and am definitely no
He must be a card carrying member of the ACLU, and now he thinks he is
the G_d of these lists :)
> -Original Message-
> From: pgsql-admin-ow...@postgresql.org
> [mailto:pgsql-admin-ow...@postgresql.org] On Behalf Of Joshua D. Drake
> Sent: Monday, February 02, 2009 4:22 PM
> To: Scott Ru
Thanks, Stephan and Milen.
Everything is clear now.
I had a change in the behavior moving from 8.1 to 8.3, and the automatic
typecasting prior to 8.3 blurred the intended behavior as per the
documentation.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your s
[EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Milen A. Radev
> Sent: Saturday, December 06, 2008 12:49 PM
> To: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Change in behavior of string concat operator
>
> Benjamin Krajmalnik написа:
> > I just migrated from 8.1
I just migrated from 8.1 to 8.3, running on FreeBSD 7.0 amd64.
Running 8.3.5
I have a query concatenating 3 columns to create a hash.
userid is a numeric(38,0) field, accountno is an integer, and
requestdate is a date.
Under 8.1, Select userid || accountno || requestdate::date as newcolumn
fro
Assuming he is using ODBC to connect, I do not believe the current ODBC
driver supports connection pooling.
My experience was that it did not. I posted a question on the ODBC
list, but have not yet received a reply.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTEC
Another option on Windows would be to get the Sysinternals utilities,
and use tcpview, which is superior to netstat.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Melissa Peterson
Sent: Tuesday, April 01, 2008 10:29 AM
T
implicitly?
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Benjamin Krajmalnik
> Sent: Wednesday, January 16, 2008 3:45 PM
> To: Ivo Rossacher; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Strange client encoding issue
&g
.
>
> Best regards
> Ivo
>
> Am Mittwoch, 16. Januar 2008 21.30:42 schrieb Benjamin Krajmalnik:
> > I am encountering a very strange client encoding issue.
> > From the logs on the server, I am getting the following:
> >
> > canopy02# tail postgresql-2008-01-
I am encountering a very strange client encoding issue.
>From the logs on the server, I am getting the following:
canopy02# tail postgresql-2008-01-16_00.log
2008-01-16 15:20:03 ESTERROR: conversion between latin9 and LATIN1 is
not supported
2008-01-16 15:20:03 ESTSTATEMENT: set client_enco
You have already posted this various times..
Have you checked with your AV provider that it is not a false positive?
I do not think it is necessary for you to be posting this every day.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Al
Toad Data Modeler
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Marco Antonio
> Sent: Monday, December 17, 2007 2:02 PM
> To: Mark Steben
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Looking for an E/R tool for Postgres
>
> On Dec 17,
Is there a way to execute an external program from within a stored
procedure?
In pl/pgsql it does not appear to be supported.
Will pl/perl allow me to do so?
A little background. I have a network monitoring platform which we
developed. The collector has the capability of issuing a single query
fo
In case you did not read my message, it started with "My apologies"
becaue I made the mistake and noticed it.
Please, do not try to lecture me. If you have something substanbtive to
reply concerning the issue I am having, then by all means do reply. I
did not know you were the self-proclaimed lis
My aplogies - I forgot to set the subject of the problem I am having
when I got lazy and used "reply".
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Benjamin Krajmalnik
> Sent: Wednesday, August 01, 2007 11:32 AM
&g
I have ascheduled pgAgent job which runs monthly executing a stored
procedure which handles some partitoned tables. Essentially, it
truncated the data in a given partitio and then it changes its rules so
it will be ready to accept the data for its respective next cycle.
The stored procedure foll
PostgreSQL Manager from EMS has one.
I recommend getting their Studio product, which integrates all of their
tools.
Definitely worth the price.
---(end of broadcast)---
TIP 6: explain analyze is your friend
D. Drake [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 12, 2007 3:39 PM
> To: Benjamin Krajmalnik
> Cc: Adam Witney; pgsql-admin@postgresql.org; Abraham, Danny
> Subject: Re: [ADMIN] How can I tell that the underlying OS is Windows?
>
> Benjamin Krajmalnik wrote:
> > My Win
My Windows box says:
"PostgreSQL 8.1.4 on i686-pc-mingw32, compiled by GCC gcc.exe (GCC)
3.4.2 (mingw-special)"
My BSD box says:
"PostgreSQL 8.1.4 on i686-pc-mingw32, compiled by GCC gcc.exe (GCC)
3.4.2 (mingw-special)"
Seems to be the same
---(end of broadcast)
select pg_postmaster_start_time()
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris Hoover
Sent: Wednesday, June 06, 2007 3:07 PM
To: pgsql-admin@postgresql.org Admin
Subject: [ADMIN] How to tell how long serve
http://www.postgresql.org/developer/roadmap
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Abraham, Danny
> Sent: Tuesday, May 08, 2007 8:25 AM
> To: pgsql-admin@postgresql.org
> Subject: [ADMIN] 8.3 and 8.4 feature list
>
> Hi,
>
> I am migrat
Aaron,
Would case studies work?
I suggest you mention the Netezza data warehousing appliance - on their
site they have comparisons against other systems which will be
impressive.
Although annecdotal, in my case I had an application running on SQL
Server. It could not keep up with the data throug
select CURRENT_TIMESTAMP
or
select LOCALTIMESTAMP
the first has the information with the timezone offset at the end,
whereas the second does not.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Negandhi, Nishith
Sent: Thursda
t connection.
> Better yet, don't make lots of tiny calls to the database if
> you can avoid it.
>
> On Mon, Dec 04, 2006 at 06:28:03PM -0700, Benjamin Krajmalnik wrote:
> > Hi Jim,
> >
> > Apples to apples (as best as I can tell).
> > The test procedu
I am battling a performance issue and was wondering if someone could
help. PostgreSQL 8.1.5, FreeBSD.
I have a very intense stored procedure which performs real time
aggregation of data.
I captured the stored procedure calls from a production system and
pumped them through psql, logging duration
I have a partitioned
table to which I route data using a trigger.
I am changing it to
use a set of rules which executes "INSTEAD" on insert.
The parent table
currently has a trigger.
The system is a live
system. I would prefer to not have to suspend the data
flow.
If I create the
rules,
.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Benjamin Krajmalnik
> Sent: Thursday, October 05, 2006 12:03 PM
> To: pgsql-admin@postgresql.org
> Subject: [ADMIN] pg_dump/pg_restore problem
>
> I have a database which has UTF8 e
I have a database which has UTF8 encoding enabled (why? I am really not
sure why I did tihs other than the source of the data is windows and I
had some issues with characters > ascii 128 being sent across from some
of the Windows event logs).
The problem which I am having is as follows:
The data
I have a problem right now where the execution time of a scheduled
stored procedure is creating an issue with our background data logging
system.
Initially I thought it may be caused due to table locks or the like, but
after much testing I have ruled that out, since data is being inserted
while the
I have a database whose records are inserted via
ODBC.
I turned on logging, and the client is explicitly setting
the client encoding to UTF.
Rows are inserted into the tables. When I do a
pg_dump, I do not get any errors. When I try tor restore, I am getting an
error regarding an invalid
a separate spindle, are there any other things
you can think of which may improve the performance?
> -Original Message-
> From: Chris Mair [mailto:[EMAIL PROTECTED]
> Sent: Monday, August 07, 2006 4:38 PM
> To: Benjamin Krajmalnik
> Cc: pgsql-admin@postgresql.org
> S
database does not
keep up with it it will stall.
Worst case, I will virtualize the monitroing agent, but that will
require quite a bit of work on our side.
> -Original Message-
> From: Chris Mair [mailto:[EMAIL PROTECTED]
> Sent: Monday, August 07, 2006 2:54 AM
> To: Benjami
1 - 100 of 151 matches
Mail list logo
