On Jul 11, 2008, at 4:24 AM, Richard Huxton wrote:
If you just want to see if a lock has been taken (e.g. SELECT FOR
UPDATE) then that shows in pg_locks. If you want details on the
actual rows involved, then you probably want "pgrowlocks" mentioned
in Appendix F. Additional Supplied Module
Here's how you do it on restore step from a pg_dump in -Fc format.
pg_restore -l dumpfile > list
edit the file "list" to remove references to slony objects
pg_restore -L list dumpfile
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
ht
On Apr 28, 2008, at 6:50 PM, [EMAIL PROTECTED] wrote:
I want to ask if there is something like nomount state or close
database state
in which I can acces postgresql to drop database or to do some other
stuff.
change the permissions on the DB so nobody can log in. you really
should find
On Apr 16, 2008, at 8:47 AM, Julio Cesar Sánchez González wrote:
From what I've read, Slony-I does only master-slave replication and
Slony-II is not being actively developed. Is this right? Are there
any
viable master-master replication tools for PostgreSQL. (They could be
commercial/paid for
On Mar 25, 2008, at 4:28 PM, Jeff Davis wrote:
This obviously does not work in real time, but it may be useful. It
does
not require a lot of additional space to do this because of the ZFS
copy-on-write implementation.
But what benefit does it give you if you're pounding on the same set
of
On Mar 17, 2008, at 10:58 PM, Tyler, Mark wrote:
I suggest rethinking your dislike of NOTIFY.
I have thought very hard about using NOTIFY for this but it has two
large problems (from my point of view). The first is that it forces me
Wait a while and you will learn to detest Spread, too.
-
On Mar 13, 2008, at 7:50 AM, Glyn Astill wrote:
I'm looking at switching out the perc5i (lsi megaraid) cards from our
Dell 2950s for something else as they're crap at raid 10.
Use an actual LSI branded card instead of the Dell "improved" version.
--
Sent via pgsql-general mailing list (pgsq
On Mar 12, 2008, at 3:19 PM, Tom Lane wrote:
- restore dump, ignoring "object already exists" errors
Couldn't one use the dump listing feature of pg_restore and comment
out the extensions when restoring? Not likely to be a big improvement
over "ignore" errors :-)
--
Sent via pgsql-gen
On Mar 11, 2008, at 2:50 PM, A. Kretschmer wrote:
i.e ... WHERE pt.created_date >= '2008-01-21'
You can't compare a date or timestamp to a varchar or text. For your
example, cast the date-string to a real date like:
Since which version of Pg?
Queries like the above have worked for me from
On Feb 20, 2008, at 2:12 PM, Douglas McNaught wrote:
Alternatively, is there a better way to streamline the duplication
of a
database?
How about:
CREATE DATABASE newdb TEMPLATE olddb;
The template DB has to have no open connections during the entire copy
process, so it is not always
On Feb 11, 2008, at 10:37 AM, Mario Lopez wrote:
The problem arises with the second type of queries, where there are
no possible partitions and that the search keywords are not known, I
have tried making indexes on the letter it ends with, or indexes
that specify that it contains the lette
On Feb 9, 2008, at 12:20 PM, Ken Johanson wrote:
But given the recent and dramatic example of 8.3's on-by-default
stricter typing in functions (now not-autocasting), I worry that
kind of change could happen in every minor version (8.4 etc).
You need to *know* your software if you're using
On Feb 4, 2008, at 11:31 AM, Joshua D. Drake wrote:
I don't agree in the least, I was actually going to suggest we add a
new one for relational design questions. I like many lists that are
contextually specific. IMO, general should be removed for example.
I think this makes sense for a web-b
On Feb 5, 2008, at 12:29 PM, Tony Caduto wrote:
So this Stonebraker guy is the Postgres Architect?
That doesn't imply Postgres == PostgreSQL :-)
The original Postgres wasn't even SQL, was it?
---(end of broadcast)---
TIP 9: In versions below
On Feb 4, 2008, at 10:00 AM, Wes wrote:
Just a follow-up on this... The REINDEX took about 2 1/2 days. I
didn't
gain much disk space back - a full backup takes just as long as
before, but
the vacuum time dropped from 30 hours to 3 hours.
what you need to do is compare the relpages from
On Jan 31, 2008, at 10:21 AM, Alvaro Herrera wrote:
Glyn Astill wrote:
I'm not piping it to a file, postgres is managing the logs. Is there
any way to manage the permissions, or do I just need to create a
script to change the permissions?
I think you should be able to chmod the files after
On Jan 31, 2008, at 10:14 AM, Erik Jones wrote:
That's an interesting idea. Is there a general audience/
participation wiki for Postgres? I know the developers have one,
but a user-oriented sister wiki would probably be a good way to get
lots of different people involved.
I'm of the opi
On Jan 31, 2008, at 4:28 AM, Aaron Glenn wrote:
CARP *and* pfsync.
this late at night off the top of my head I can't see any blatantly
obvious reason this wouldn't work (with at least pgpool that is, dunno
about your data)
we use CARP to balance and failover some webserver pairs. We also use
On Jan 29, 2008, at 7:24 AM, Glyn Astill wrote:
I'm trying yo run a perl script that uses DBI (Slonys
psql_replication_check.pl to be precise) and I'm getting the error:
Can't locate Pg.pm in @INC
It doesn't use DBI, it uses Pg. At some point I posted patches to
convert it to DBI and DBD
On Jan 23, 2008, at 10:26 AM, Tom Lane wrote:
Reading the release notes is good, but you really really should test
the
application(s) against a test 8.1 installation before you go live ...
be sure to run *every* query your system uses through 8.1. the most
common problems you will run in
On Dec 21, 2007, at 11:09 AM, Martijn van Oosterhout wrote:
The usual answer is use slony. You can use it to replicate the 8.0
server onto an 8.1 server. This may take weeks/months/years/whatever
to
synchronise. When the slave is up to date, you pull the plug on the
8.0
server and get ever
On Dec 11, 2007, at 10:44 AM, Gregory Stark wrote:
The problem Tom's tried to explain is that the function may or may not
preserve the bin. So for example if you wanted to bin based on the
final digit
of a numeric number, so you had a constraint like
I, along with at least Erik, was thinki
On Dec 11, 2007, at 10:08 AM, Erik Jones wrote:
b.) precomputing the bin and directly accessing the child table will
be the only options we have for now.
This is where I'm headed I have only one or two queries that don't
specify the partitioned ID, and those need a full table scan anyh
On Dec 10, 2007, at 5:04 PM, Colin Wetherbee wrote:
For what it's worth, the real algorithm would be as follows. I
hadn't had enough coffee yet, and I forgot the UPDATE bit.
IF
(a query matching your old data returns rows)
THEN
UPDATE with your new data
ELSE
INSERT your new data
Still
please don't hijack old threads ("partitioned table query question" in
this case) and change the subject line to start your new question. it
messes up threaded mail readers.
thanks.
On Dec 10, 2007, at 3:00 PM, Nathan Wilhelmi wrote:
Hello - Does anyone happen to have a SQL script or funct
On Dec 10, 2007, at 1:21 PM, Erik Jones wrote:
You beat me to the punch on this one. I was wanting to use modulo
operations for bin style partitioning as well, but this makes things
pretty awkward as well as unintuitive. So, to the postgres gurus:
What are the limitations of check cons
On Dec 7, 2007, at 11:42 AM, Colin Wetherbee wrote:
You can do this with a conditional. Something like the following
should work.
IF
NOT (a query matching your data returns rows)
THEN
INSERT (your new data)
There exists a race condition here unless you've locked your tables.
--
On Dec 8, 2007, at 9:21 AM, Geoffrey wrote:
I am quite new to Slony as well, but one of the first requirements
the docs state is:
Thus, examples of cases where Slony-I probably won't work out well
would include:
* Sites where connectivity is really "flakey"
* Replication to nodes t
On Nov 28, 2007, at 11:17 AM, Glyn Astill wrote:
I've already tried removing and re-installing bison, but I shall try
again as you suggest.
I recommended uninstalling bison, not re-installing it.
---(end of broadcast)---
TIP 6: explain analyz
On Nov 28, 2007, at 11:06 AM, Matt Doughty wrote:
Is there a way of selecting all fields except for one in particular?
I'd like to create a query that says something like:
select * except fieldx
For best practices, you should never use select * in your queries.
You will inevitably end
On Nov 28, 2007, at 8:50 AM, Glyn Astill wrote:
Hi people,
When I try to compile Slony 1.2 I get the following error:P
parser.y:1090:18: error: scan.c: No such file or directory
make[2]: *** [parser.o] Error 1
make[2]: Leaving directory `/tmp/slony1-1.2.12/src/slony_logshipper'
make[1]: *** [
On Nov 28, 2007, at 8:18 AM, Richard Huxton wrote:
I can read that I can create a PostgreSQL DB on the RAMDisk
partion, but I'm wondering if is it possible to create
one DB with two schemas in two different memory location (RAM and
flash)?
See the manuals for "tablespaces".
but postgres
tions.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D.MailerMailer, LLC Rockville, MD
http://www.MailerMailer.com/ +1-301-869-4449 x806
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
On Nov 26, 2007, at 10:14 AM, Jeff Larsen wrote:
Yes, but I'd like something better than "near real time" as the above
page describes. Or maybe someone could clarify that Besides,
EnterpriseDB does not save me enough money. In my current commercial
DB, if a transaction is committed on the m
On Nov 24, 2007, at 6:18 PM, Laurent CARON wrote:
Question:
I'd like to know if it is possible (and wise) to just keep the
/var/lib/postgres.. directories from the old 32Bit server to use
on
the 64Bit version.
This is just as a personal interest since I can also just dump and
restore th
On Nov 20, 2007, at 1:04 PM, Josh Harrison wrote:
I ran vacuum full on this table already. I haven't re-indexed it. But
this will not affect the table size...right...since indexes are stored
separately?
Yes, but your indexes are probably bloated at this point, so to reduce
the space they
On Nov 13, 2007, at 1:18 PM, [EMAIL PROTECTED] wrote:
Yep, this is a fork without exec. And the child processes often aren't
even doing any database access -- the database connection's opened and
held, then a child is forked off, and the child 'helpfully' closes the
handle during the child's gl
On Nov 12, 2007, at 8:55 PM, Steve Manes wrote:
Steve Manes wrote:
What's the portupgrade process in FreeBSD??
(Fixed. The answer is to use pg_delete -f on the old package to
force the delete)
more elegantly,
portupgrade -Rrv -f -o databases/postgresql82-client postgresql-client
but y
On Nov 12, 2007, at 12:01 PM, Greg Smith wrote:
Not the Mac OS BSD. Last time I looked into this OS X was still
dramatically slower than Linux on things like process creation.
On MacOS X, that's the Mach kernel doing process creation, not
anything BSD-ish at all. The BSD flavor of MacOS
On Nov 12, 2007, at 12:29 PM, Sam Mason wrote:
You only need a 64bit address space when each process wants to see
more
than ~3GB of RAM.
And how exactly do you get that on a 32-bit CPU? Even with PAE
(shudders from memories of expanded/extended RAM in the DOS days), you
still have a 32
On Nov 1, 2007, at 8:51 PM, Ow Mun Heng wrote:
Another question is, based on what I've read in the archives (in my
laptop.. No-Inet conn @ work) Since I've overran my max_FSM, I'm
basically screwed and will have to do a vacuum verbose FULL on the
entire DB. Crap..
I've seen this repeated many
On Oct 5, 2007, at 9:10 AM, Kenneth Downs wrote:
I also found it very hard to pin down the penalty of the trigger,
but came up with rough figures of 30-50% overhead. The complexity
of the trigger did not matter.
in which language did you write your triggers?
---(
On Sep 28, 2007, at 9:07 AM, Ottavio Campana wrote:
But why does pg_dump does not already exports data such that previous
tables do not depend on successive ones?
Because you can't always sort your tables that way. The restore
procedure is responsible for either sorting or disabling the FK
On Sep 28, 2007, at 5:09 AM, Tom Allison wrote:
I know reiserfs does better performance wise, but there's no point
in going fast if you can't steer.
I recently had to replace 16 Western Digital 10kRPM SATA drives with
Hitachi 7.2kRPM drives because the WD drives kept randomly (and
falsel
On Sep 24, 2007, at 12:00 PM, Phoenix Kiula wrote:
I feel your pain. But I seem to have (mostly) solved my problem in
three ways:
My particular usage pattern (add data continuously, purge *some* of
the data once per week or every other week. The purge is what seems
to kill it. Last tim
On Sep 18, 2007, at 1:14 AM, Joshua D. Drake wrote:
Q: To get rid of index bloat, is a VACUUM ANALYZE enough? Or must I
reindex/cluster indexes?
If you overrun your max_fsm_pages, no:
else yes;
my algorithm is: if (true) then yes;
my FSM is way bigger than I ever use (vacuum never report
On Sep 12, 2007, at 7:32 PM, Andrew Hammond wrote:
Does anyone know where I could find a tool which allows importing
schema information from a postgres database into visio? The boss
guys want some pretty pictures...
See SQLFairy. it can generate pretty pictures directly from the
schemas
On Aug 30, 2007, at 4:03 AM, Ow Mun Heng wrote:
2. how do I perform a list of SQL using transactions. eg: like above,
but wrap it into a transaction.
assuming $dbh is your open handle to the database via DBI, then you
do something like this:
$dbh->begin_work() or die;
$sth = $dbh->prepare
On Aug 27, 2007, at 11:04 AM, Andrew Sullivan wrote:
It was a way to scale many small systems for certain kinds of
workloads. My impression is that in most cases, it's a SQL-ish
solution to a problem where someone decided to use the SQL nail
because that's the hammer they had. I can think of
On Aug 25, 2007, at 8:12 AM, Phoenix Kiula wrote:
The sentence that caught my attention is "Nokia, Alcatel and Nortel
are all building real-time network nodes on top of MySQL Cluster."
My experiences with MySQL so far have been less than exhilerating
(only tried it for our web stuff, which is
On Aug 25, 2007, at 1:34 AM, Benjamin Arai wrote:
There has to be another way to do incremental indexing without
loosing that much performance.
This is the killer feature that prevents us from using the tsearch2
full text indexer on postgres. we're investigating making a foreign
table f
On Aug 24, 2007, at 4:09 AM, Alban Hertroys wrote:
I'm not entirely sure what makes multi-threading be advantageous on a
specific operating system, but I think FreeBSD should be added to that
list as well... They've been bench marking their threading support
using
multi-threading in MySQL (n
On Aug 15, 2007, at 7:41 AM, Ivan Zolotukhin wrote:
What is the best practice to process such a broken strings before
passing them to PostgreSQL? Iconv from utf-8 to utf-8 dropping bad
characters?
This rings of GIGO... if your user enters garbage, how do you know
what they wanted? You don'
On Aug 9, 2007, at 9:38 AM, Brad Nicholson wrote:
I have the times that it takes to to do a regular
vacuum on the clusters, will vacuum full take longer?
almost certainly it will, since it has to move data to compact pages
rather than just tagging the rows as reusable.
you can speed thing
On Aug 1, 2007, at 10:56 AM, Richard Huxton wrote:
You could write a small cron-script that dumped the schema once
every 5 minutes so it could be picked up by svn.
I think most people have a separate collection of schema-creation/
update scripts that they keep under version control. All cha
On Jul 27, 2007, at 8:29 PM, Jim Nasby wrote:
Double-check with the Slony guys, but ISTR that there's an issue
going all the way from 7.4 to 8.2 in a single shot.
I don't think that's a slony-specific issue. Moving from 7.4 to 8.0
introduces a fair number of incompatibilities one must add
On Jul 16, 2007, at 9:26 AM, Francisco Reyes wrote:
I guess the next question is 'what does postgresql considers a blob'?
bytea fields? How about a large text with megabytes worth of data?
bytea and text fields are NOT blobs. they are what you access via
the 'large object' functions.
--
On Jun 26, 2007, at 3:31 PM, Bill Moran wrote:
VACUUM FULL and REINDEX are not required to maintain disk usage.
Good old-
fashoned VACUUM will do this as long as your FSM settings are high
enough.
I find this true for the data but not necessarily for indexes. The
other week I reindex
On Jun 25, 2007, at 10:32 PM, Francisco Reyes wrote:
Hm... now I am really confused.
The same settings on AMD64 work. So how are "more resources
available" when I have the same amount of memory and the same
settings?
you set your maxdsize to the same as on i386? on even my smallest
am
On Jun 25, 2007, at 9:33 PM, Francisco Reyes wrote:
Therefore, the problem is only with the i386 version.
Should I report this as a bug or is this "nornal" and expected?
i wouldn't call it a bug to need more resources than you've got
available :-) obviously the limits on the i386 version
On Jun 18, 2007, at 2:10 PM, Francisco Reyes wrote:
Also the error is about running out of memory when trying to
allocate 84MB.
The default FreeBSD limit is 512MB so 84MB is well below that.
Try being less stingy than 128Mb for your stack. The default stack
is 512Mb.
--
On Jun 15, 2007, at 8:24 AM, Francisco Reyes wrote:
Understood. But at least it shows that the program was already
above the default of 512MB limit of the operating system.
But that is a false assertion that the limit is 512Mb. On a random
system of mine running FreeBSD/i386 it shows the
On Jun 8, 2007, at 3:33 PM, Guy Rouillier wrote:
Well, I'm not one of the developers, and one of them may have this
particular scratch, but in my opinion just about any available fish
has to be bigger than this one. Until someone comes out with a
standardized approach for utilizing whatev
On May 25, 2007, at 5:28 PM, Tom Lane wrote:
That's true at the level of DDL operations, but AFAIK we could
parallelize table-loading and index-creation steps pretty effectively
--- and that's where all the time goes.
I would be happy with parallel builds of the indexes of a given
table. T
On May 23, 2007, at 1:12 PM, Donald Laurine wrote:
Now my question. The performance of each of these databases is
decreasing. I measure the average insert time to the database. This
metric has decreased by about 300 percent over the last year. I run
vacuum analyze and vacuum analyze full o
On May 15, 2007, at 10:35 AM, Bill Moseley wrote:
For some value of "large", is there a time when one might consider
using a single column in the user or user_prefs table to represent
their color choices instead of a link table?
We use bitfields on our large user table. It is becoming unwork
On May 14, 2007, at 4:37 PM, Bill Moseley wrote:
Say that there's also about 10 columns of settings or preferences for
each user. Are there any cases or reasons to have a separate
"user_preferences" table vs. just placing all the columns together in
one table?
when you have, say 65 million u
On May 13, 2007, at 10:43 PM, Tom Lane wrote:
It's hard to make any money that way :-(. Rich Morin used to run a
business called "Prime Time Freeware" that published hardcopy versions
of our manuals along with much other open-source documentation.
He gave up on it some years ago, though, and I
On Apr 9, 2007, at 10:09 AM, [EMAIL PROTECTED] wrote:
It would be a really great service to this community if you would
capture those issues and publish documentation (but feel free to
change or omit the names to protect the incompetent^w innocent!).
There's no incompetence involved... the
On Mar 27, 2007, at 4:09 PM, Tony Caduto wrote:
Another thing is this, how hard could it possibly be for a MS SQL
DBA or Oracle DBA to pick up using PostgreSQL?
I don't think it would take a decent admin of any database to come
up to speed in a very short time as long as they were interested
On Mar 21, 2007, at 3:09 PM, Bill Eaton wrote:
I want to allow some queries for my users to run for a prescribed
period
of
time and kill them if they go over time. Is there a good way to
do this?
set statement_timeout perhaps?
Ooh. I like that. It would be absolutely brilliant if I cou
On Mar 19, 2007, at 1:58 AM, ab wrote:
I am trying to measure the time taken for a number of queries using
\timing .
All queries on my table other than the first one are pretty fast. This
is likely due to caching. Is there any way to clear the internal cache
of Postgres. Should I be worried abo
hanks!
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D.Khera Communications, Inc.
Internet: khera@kciLink.com Rockville, MD +1-301-869-4449 x806
---(end of broadcast)---
TIP 2: Don't &#x
On Mar 15, 2007, at 10:22 AM, Alvaro Herrera wrote:
He could wait for 8.4 as well, as it will be probably faster and have
more features than 8.3. Following your reasoning, one could wait
essentially forever.
H... precisely the reason my cell phone hasn't been replaced in a
long tim
On Mar 14, 2007, at 2:00 PM, Tom Lane wrote:
Should work to just copy over the timezone directory tree from a
correct
installation on the same machine architecture (I can't recall right
now
if the file format is machine-dependent or not). You might have to
restart the postmaster too, befor
On Mar 12, 2007, at 6:08 PM, Martijn van Oosterhout wrote:
On Mon, Mar 12, 2007 at 01:13:42PM -0600, Ed L. wrote:
Would I be correct in understanding that every pre-8.0 cluster
must be restarted in order for the OS changes to take affect?!?
Possibly, I imagine many C libraries would cache th
On Mar 14, 2007, at 11:36 AM, Richard Huxton wrote:
Vivek Khera wrote:
I want to do some debugging on an app, and I'd like to set on a
per-connection basis "set log_min_duration_statement = 10;"
Obviously since I'm not super user I get permission denied.
Is there some
I want to do some debugging on an app, and I'd like to set on a per-
connection basis "set log_min_duration_statement = 10;" Obviously
since I'm not super user I get permission denied.
Is there some GRANT I can grant to the user in question to allow
this? I don't really want to do it globa
On Mar 6, 2007, at 3:42 AM, veejar wrote:
Hi!
I have server such configuration:
2 x Xeon LV DualCore 1.66GHz
MEM 4Gb DDR2-400
2 x 250Gb SATA HDD
how are you using the drives? software mirror?
I have 20 databases on PostgreSQL 8.
2 of them are more than 1GB.
I have ~50 requests per second.
On Feb 28, 2007, at 5:35 PM, Bill Moran wrote:
Just an FYI ... I remembered what prompted the cron job.
We were seeing significant performance degradation. I never did
actual
measurements, but it was on the order of "Bill, why is restoring
taking
such a long time?" from other systems peop
On Feb 16, 2007, at 4:13 PM, Andrew Kirkness wrote:
I am currently setting up a website and have PostGreSQL database
I'm using for the backend. I'm researching an open source Content
Management System that uses PostGreSQL. Do you have any
recommendations?
You need to define what you want
On Feb 16, 2007, at 12:46 PM, Ezequias Rodrigues da Rocha wrote:
Hi list,
I am looking for this guy for some help with Slony-I.
Then why don't you send Robert a direct email? He's not that hard to
find with google.
Or perhaps ask your question here; there are lots of smart folks
here
On Jan 27, 2007, at 10:45 AM, Ron Johnson wrote:
Using slony or "piped pg_dump" requires that you have *double* the
amount of disk space. Having a *very large* database and double
capacity of SCSI disks (including storage controllers, shelves, etc,
etc) is expensive, and might not be available
On Jan 17, 2007, at 11:56 AM, Tom Lane wrote:
So the above doesn't sound too unlikely. Perhaps we should recommend
vac full + reindex as standard cleanup procedure. Longer term, maybe
teach vac full to do an automatic reindex if it's moved more than X
% of
a vac full + reindex is a waste o
On Jan 3, 2007, at 2:00 AM, Steve Atkins wrote:
Holding a lock while generating the thumbnail doesn't
sound like a great idea, and I think that the select
for update will end up serialising the requests.
I'd add a "rendering" field, text, defaulting
to an empty string.
Then do a "select for u
On Dec 19, 2006, at 3:17 AM, Jeff Amiel wrote:
We have a production FreeBSD 6.0 system with Postgresql 8.1 where we
have avoided upgrading/updating the ports to avoid compatability and
other unknown issues.
We have our supfile default date set on our production, test and
development environment
On Dec 5, 2006, at 5:07 PM, Josh Berkus wrote:
Ragnar,
Now that this has been announced, should not
http://www.postgresql.org/docs/current/ and co be
redirected to http://www.postgresql.org/docs/8.1/
instead of http://www.postgresql.org/docs/8.2/
in particular, the press release's link to the
On Dec 5, 2006, at 4:09 PM, Scott Marlowe wrote:
I recently tossed 8.1 on my workstation which runs a little reporting
application here. I pointed the app from 7.4 to 8.1 and got a visit
within about an hour from a user, asking if I'd done anything to my
database. Worrying that I'd made some
On Nov 30, 2006, at 8:50 AM, Enrico wrote:
I already read your link and it is not specific for Postgres, I'm
searching for a
more specific document.
Just remove any devices you don't have on your machine, and remove
any "extras" like linux compat, older version compat, etc. You
probabl
On Nov 29, 2006, at 2:39 PM, Scott Marlowe wrote:
Sounds good. According to LSI, the drive will take 8 hrs to rebuild a
146GB disc (at a 30% rebuild rate), so doing this in the middle of
the
day is not ideal.
The rebuild time also tends to depend on how full the array is. If
you're only u
On Nov 29, 2006, at 11:56 AM, Steve Poe wrote:
I've never had to replace a disc in an array with Postgresql
running on it. LSI says I can replace the disc and do a rebuild
while everything is running. I am of course concerned about data
integrity/corruption.
This is the whole entire co
On Nov 28, 2006, at 11:11 AM, Andrus wrote:
1. My database size seems to be appox 1 GB and download speed is
approx 600
kb/s. Your solution requires 4.5 hours download time
since 1 GB of data must be downloaded.
If you're running pg_dump on a remote host, you're transferring the
data ove
On Nov 28, 2006, at 8:40 AM, Jakub Ouhrabka wrote:
There are 4G of RAM and 4G swap.
and what is the per-process resource limit imposed by your OS?
Just because your box has that much RAM doesn't mean your process is
allowed to use it.
smime.p7s
Description: S/MIME cryptographic signatu
On Oct 25, 2006, at 10:11 AM, A. Kretschmer wrote:
Set this in your postgresql.conf:
log_statement = all
Reload the server, and then you can find all your statements in the
log.
or, preferably, on a per-connection basis, execute this SQL statement:
set log_min_duration_statement = 0
the
On Oct 17, 2006, at 2:35 PM, Steve Poe wrote:
Vivek,
What methods of backup do you recommend for medium to large
databases? In our example, we have a 20GB database and it takes 2
hrs to load from a pg_dump file.
my largest db is about 60Gb with indexes. reloading the data (about
30G
On Oct 17, 2006, at 10:43 AM, [EMAIL PROTECTED] wrote:We just tar/gzip the entire data directory. It takes all of 20 sec. We've successfully restored from that also. The machine you are restoring to *must* be running the save version of postgresql you backed up from. If you successfully backed u
On Oct 16, 2006, at 1:15 PM, Brandon Metcalf wrote:
Does anyone know of any issues with continuing to use the old Pg
interface with newer versions of PostgreSQL?
it is just a rather thin glue layer on top of the libpq interface, so
it should continue to work just as any libpq app would cont
On Oct 16, 2006, at 1:08 PM, Carlos H. Reimer wrote:
How can we explain the 01:00:00 hour that the to_date function
returns for
date 15/10/2006?
does your timezone change from summer time to winter time (daylight
savings, etc.) on that date?
smime.p7s
Description: S/MIME cryptographic
On Oct 11, 2006, at 2:55 PM, snacktime wrote:
So by putting all the data into one schema, every report query now
gets run against a million or more rows instead of just a few hundred
or thousand. So all clients will see a drop in query performance
instead of just the clients with large amount
On Sep 22, 2006, at 1:03 PM, Jim C. Nasby wrote:
Berkus doesn't count??! He's got long hair! What more do you want?!
Well, then based on volume he should count as two :-)
No offense intended, Josh... *I'd* count as two, too.
smime.p7s
Description: S/MIME cryptographic signature
1 - 100 of 273 matches
Mail list logo
