W dniu 2013-04-21 19:28, Scott Marlowe pisze:
My DB version is little old - 8.1.18.
Well upgrade as soon as possible. 9.1 is pretty darn stable.
Scott,
excuse me this somewhat off-topic question.
Good to hear that 9.1 is so stable, because this is what I currently use in production. But why
W dniu 2013-02-14 16:35, Nicolas Charles pisze:
I'm crunching the data by looking for each nodeid/ruleid/directiveid/serial with an
executiontimestamp in an interval:
explain analyze select executiondate, nodeid, ruleid, directiveid, serial, component, keyValue,
executionTimeStamp, eventtype,
er port your server runs on) has some problems on the connection
route. Stop the server and use the nc (or netcat) utility on the two machines talking to each other
on this port.
Just use the tools Linux gives you, understand what happens behind the scenes.
Hope this helps
Irek.
Any other idea
estion: Why "libpq" is faster on Windows than Linux?.
try to benchmark your elementary queries with psql run from your site (remotely to the server) and
from remote site (locally to the server). Use `psql -h hostaddr` at remote site to force tcp connection.
Best regards...
Ariel Rodrigu
W dniu 2012-09-06 22:04, Aryan Ariel Rodriguez Chalas pisze:
-Why if I connect to the remote server desktop (using RDP or any Remote Desktop
Application) and run the application using the same internet connection, it runs really
fast when making requests to postgresql; but if I run the applicat
Achilleas Mantzios wrote:
How are you gonna show up in the FreeBSD-* mailing list when you are still on
6.2?
Psst! - I came just here. Don't tell them.
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.or
Scott Marlowe wrote:
If I may ask, how often does it crash? And have you tried updating
the firmware of the controller and / or the driver in the OS?
It happens once per two or three months, or so, taking the average. The firmware is beta as of
January this year, advised to use by their technic
Scott Marlowe wrote:
If I may ask, how often does it crash? And have you tried updating
the firmware of the controller and / or the driver in the OS?
It happens once per two or three months, or so, taking the average. The firmware is beta as of
January this year, advised to use by their technic
Greg Smith wrote:
The soft update code used in FreeBSD makes sure that there's no damage to the filesystem that
PostgreSQL can't recover from. Once the WAL is replayed after a crash, the database is
consistent. The main purpose of the background fsck is to find "orphaned" space, things that th
Achilleas Mantzios wrote:
In anyway, having FreeBSD to fsck, (background or not) should not happen. And
the problem
becomes bigger when cheap SATA drives will cheat about their write cache being
flushed to the disk.
So in the common case with cheap hardware, it is wise to have a UPS connected
But waiting so much time (like now) during foreground fsck of a large data
filesystem after unclean shutdown, makes me to come to this group to ask
whether I really need to avoid background fsck on a PostgreSQL machine?
Could I hear your opinions?
Shouldn't a journaling file system just come bac
Hello,
I saw some recommendations from people on the net not to use background fsck when running PostgreSQL
on FreeBSD. As I recall, these opinions were just thoughts of people which they shared with the
community, following their bad experience caused by using background fsck. So, not coming a
Greg Smith pisze:
The MegaRAID SAS 84* cards have worked extremely well for me in terms
of performance and features for all the systems I've seen them
installed in. I'd consider it a modest upgrade from that 3ware card,
speed wise.
OK, sounds promising.
The main issue with the MegaRAID ca
Hello,
I am waiting for an ordered machine dedicated to PostgresSQL. It was
expected to have 3ware 9650SE 16 port controller. However, the vendor
wants to replace this controller with MegaRAID SAS 84016E, because, as
they say, they have it on stock, while 3ware would be available in a few
wee
possibilities of not to have to restore two copies of my data, but use just one instead, and sharing
it between the 32 and 64 versions, across reboots.
Would that scenario work, or I am simply too naive considering it?
Thanks
Ireneusz Pluta
PS.
Or rather, instead of testing 32/64 bit, I would just
ty of Promise.
Is this technically a good idea to take Promise instead of 3ware or rather I definitely should
insist on 3ware and wait for it?
Thank you
Ireneusz Pluta
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL proje
, with exceptinos for overnight periods, when bulk data is inserted
and updated.
Thank you
Ireneusz Pluta
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining
jamcito napisał(a):
/*/
SET constraint_exclusion=on;
SET
SHOW constraint_exclusion;
constraint_exclusion
--
on
(1 row)
EXPLAIN SELECT * FROM data WHERE name = 'aaa';
QUERY PLAN
-
18 matches
Mail list logo
