On Jan 18, 2013, at 4:26 PM, Rich Shepard wrote:
> On Fri, 18 Jan 2013, Adrian Klaver wrote:
>
>> How are they stored, as date and time type, strings, other?
>
> Adrian,
>
> ISO date and time.
>
>> A sample of the data would help also.
>
> Example: 2012-10-29 | 10:19 | 2012-10-30 |
or otherwise).
I ask largely because we use prepared statements everywhere and this makes it
very hard
to use partial indices, which would offer us significant performance gains.
Does anyone know of any acceptable workaround? Is there continued interest in
maybe improving the PostgreSQL behavior
On Feb 6, 2013, at 8:14 AM, Roberto Scattini wrote:
> hi list,
>
> we have two new dell poweredge r720. based on recommendations from this list
> we have configued the five disks in raid10 + 1 hot spare.
You might mention a bit more about how your drives are configured. 5 drives in
a RAID1+
On Feb 6, 2013, at 9:55 AM, Roberto Scattini wrote:
>
> hi steven,
>
> > we have two new dell poweredge r720. based on recommendations from this
> > list we have configued the five disks in raid10 + 1 hot spare.
>
> You might mention a bit more about how your drives are configured. 5 drives
On Mar 12, 2013, at 8:09 PM, Joe Van Dyk wrote:
> On Mar 12, 2013, at 8:42 AM, Perry Smith wrote:
>
>>
>> The other thought is perhaps there is a "snap shot" type concept. I don't
>> see it in the list of SQL commands. A "snap shot" would do exactly what it
>> sounds like. It would take
On Apr 9, 2013, at 11:25 AM, Scott Marlowe wrote:
> One of the most common causes I've seen for this is linux's vm.*dirty*
> settings to get in the way. Like so many linux kernel "optimizations" this
> one looks good on paper but gives at best middling improvements with
> occasional io storms
Hi everyone,
I have a large table (~150M rows) that keeps a version field. At any given
time, it is expected that the vast majority of the rows are on the "current"
version, but some may be missing.
To figure out all the missing our outdated values, I run a query along the
lines of
SELECT id
On Apr 22, 2013, at 12:47 PM, akp geek wrote:
> pg_dump dbname -n schemaname -t table_name -Fc | split -b 500m -t table.dump
Since you split the files outside of the Postgres world, you have to combine
them again. Roughly,
cat table.dump.* > table.dump.combined
pg_restore --usual-arguments t
On Apr 30, 2013, at 4:00 PM, "Carlo Stonebanks"
wrote:
> Hi Tom,
>
>>> There's nothing obviously wrong with that, which means the issue is in
> something you didn't show us. Care to assemble a self-contained example?
> <<
>
> Unfortunately, it happens erratically and very, very rarely so I c
On May 1, 2013, at 9:36 AM, "Carlo Stonebanks"
wrote:
> I have to ask myself, is it more likely that I have discovered some PG
> anomaly in 9.0 that no one has ever noticed, or that the client has
> accidentally launched the process twice and doesn't know it?
Given my (admittedly limited) exper
On May 10, 2013, at 7:14 AM, Matt Brock wrote:
> Hello.
>
> We're intending to deploy PostgreSQL on Linux with SSD drives which would be
> in a RAID 1 configuration with Hardware RAID.
>
> My first question is essentially: are there any issues we need to be aware of
> when running PostgreSQL
On May 10, 2013, at 11:38 AM, Merlin Moncure wrote:
>>
>> PostgreSQL configuration changes:
>> synchronous_commit = off
>>
>
> that's good info, but it should be noted that synchronous_commit
> trades a risk of some data loss (but not nearly as much risk as
> volatile storage) for a big increa
On May 10, 2013, at 11:35 AM, Lonni J Friedman wrote:
>>
>> I am not sure that these numbers will end up being anywhere near what works
>> for you, but these are my notes from tuning a 4xMLC SSD RAID-10. I haven't
>> proven that this is optimal, but it was way better than the defaults. We
>
On May 15, 2013, at 11:52 PM, Thomas Kellerer wrote:
> Sajeev Mayandi, 16.05.2013 07:01:
>> Hi,
>>
>> Our company is planning to move to postreSQL. We were initially using
>> sybase where upsert functionality was available using "insert on
>> existing update" clause. I know there multiple ways
Hi everyone,
I assume this is not easy with standard PG but I wanted to double check.
I have a column that has a very uneven distribution of values. ~95% of the
values will be the same, with some long tail of another few dozens of values.
I want to have an index over this value. Queries that
On Jun 18, 2013, at 12:23 PM, John R Pierce wrote:
> On 6/18/2013 12:17 PM, Steven Schlansker wrote:
>> 1) The common value is not known at schema definition time, and may change
>> (very slowly) over time.
>
> how could a value thats constant in 95% of the rows change, u
On Jun 18, 2013, at 1:49 PM, David Johnston wrote:
> Steven Schlansker-3 wrote
>> At some point, the code changes, and CURRENT_VERSION gets incremented.
>> Rows then slowly (over a period of days / weeks) get "upgraded" to the new
>> current version, in batch
On Jun 18, 2013, at 2:29 PM, Jeff Janes wrote:
> On Tue, Jun 18, 2013 at 12:17 PM, Steven Schlansker
> wrote:
> Hi everyone,
>
> I assume this is not easy with standard PG but I wanted to double check.
>
> I have a column that has a very uneven distribution of values.
On Jun 26, 2013, at 11:04 AM, pg noob wrote:
>
> Hi all,
>
> There are some places in our application where unique constraint violations
> are difficult to avoid due to multithreading.
> What we've done in most places to handle this is to retry in a loop.
>
> Generally it starts by checking
On Jul 8, 2013, at 6:48 AM, Jov wrote:
> netstat show nothing about the socket of the process,so I think the TCP
> timeout took effect.so it is really wired.
>
> Jov
> blog: http:amutu.com/blog
>
>
> 2013/7/8 Tom Lane
> Merlin Moncure writes:
>> On Mon, Jul 8, 2013 at 4:56 AM, Jov wrote:
>
On Jul 8, 2013, at 6:48 AM, Jov wrote:
> netstat show nothing about the socket of the process,so I think the TCP
> timeout took effect.so it is really wired.
>
> Jov
> blog: http:amutu.com/blog
>
>
> 2013/7/8 Tom Lane
> Merlin Moncure writes:
> > On Mon, Jul 8, 2013 at 4:56 AM, Jov wrote:
PostgreSQL 9.0 High Performance: http://www.amazon.com/books/dp/184951030X
On Jul 18, 2013, at 3:11 PM, Pedro Costa wrote:
> Hi guys,
>
> Can anyone tell me the best books about postgresql? Specialy about tunning
> and querys performances
> Thanks
>
>
>
> Enviado do meu tablet Samsung
On Sep 11, 2013, at 4:29 PM, Gregory Haase wrote:
> I was trying to figure out how to get the following syntax to work:
>
> echo "select pg_start_backup('zfs_snapshot'); \\! zfs snapshot
> zroot/zpgsql@test; \\ select pg_stop_backup();" | psql postgres
I do:
psql -c "select pg_start_backup('
On Sep 25, 2013, at 6:04 AM, Merlin Moncure wrote:
> On Tue, Sep 24, 2013 at 10:19 PM, François Beausoleil
> wrote:
>> Hi all!
>>
>> I import many, many rows of data into a table, from three or more computers,
>> 4 times per hour. I have a primary key, and the query I use to import the
>> da
On Sep 26, 2013, at 10:55 AM, Craig Boyd wrote:
> Dmitriy,
>
> Thank you very much for the reply!
>
> Right...got the the data type...but how do I actually insert a binary string
> into the column? What does the SQL look like?
> For the moment assume I have the following bit of binary: 4PO
On Sep 26, 2013, at 6:35 AM, "Kohler Manuel"
wrote:
> Hi,
> we are developing a Java based software with Postgres as a DB.
> Could someone tell me if there will be a JDBC driver for 9.3 out soon or
> is it safe and recommended to use the latest JDBC driver available?
> Currently we are using:
>
On Sep 26, 2013, at 10:28 PM, mdr wrote:
>
> create user import_dbms_user with password 'import_dbms';
> create database import_dbms_db;
> grant all privileg
> However when I try to run psql from the command line:
> psql -h localhost -U import_dbms_user -WI enter password when prompted
> Passwo
Hi everyone,
I’ve seen murmuring on the list regarding
https://wiki.postgresql.org/wiki/Nov2013ReplicationIssue
Is there an ETA on a release with the bug fix for this? I’m putting off
building from source because I prefer to use the pgdg RPM packages, but if we
don’t get a release soon it mig
On Dec 3, 2013, at 2:15 PM, Tom Lane wrote:
> Steven Schlansker writes:
>> I’ve seen murmuring on the list regarding
>> https://wiki.postgresql.org/wiki/Nov2013ReplicationIssue
>
>> Is there an ETA on a release with the bug fix for this? I’m putting off
>>
> On Mar 12, 2014, at 10:12 AM, Daryl Foster wrote:
>
> java.lang.ClassCastException: org.postgresql.geometric.PGpath cannot be cast
> to org.postgresql.geometric.PGpath
>
That's a sure sign of ClassLoader confusion. Make sure there is only one copy
of the driver jar in your application or
Hi everyone,
I have a Postgres 9.3.3 database machine. Due to some intelligent work on the
part of someone who shall remain nameless, the WAL archive command included a
‘> /dev/null 2>&1’ which masked archive failures until the disk entirely filled
with 400GB of pg_xlog entries.
I have fixed
On Mar 25, 2014, at 3:52 PM, Adrian Klaver wrote:
> On 03/25/2014 01:56 PM, Steven Schlansker wrote:
>> Hi everyone,
>>
>> I have a Postgres 9.3.3 database machine. Due to some intelligent work on
>> the part of someone who shall remain nameless, the WAL arc
On Mar 25, 2014, at 4:02 PM, Adrian Klaver wrote:
> On 03/25/2014 03:54 PM, Steven Schlansker wrote:
>>
>> On Mar 25, 2014, at 3:52 PM, Adrian Klaver wrote:
>>
>>> On 03/25/2014 01:56 PM, Steven Schlansker wrote:
>>>> Hi everyone,
>>>>
On Mar 25, 2014, at 4:45 PM, Adrian Klaver wrote:
> On 03/25/2014 04:17 PM, Steven Schlansker wrote:
>>
>> On Mar 25, 2014, at 4:02 PM, Adrian Klaver wrote:
>>
>>> On 03/25/2014 03:54 PM, Steven Schlansker wrote:
>>>>
>>>> O
On Mar 25, 2014, at 7:58 PM, Adrian Klaver wrote:
> On 03/25/2014 04:52 PM, Steven Schlansker wrote:
>>
>
>>> Some more questions, what happens when things begin to dawn on me:)
>>>
>>> You said the disk filled up entirely with log files yet currently t
On Mar 26, 2014, at 9:04 AM, Jeff Janes wrote:
> On Tue, Mar 25, 2014 at 6:33 PM, Jeff Janes wrote:
> On Tuesday, March 25, 2014, Steven Schlansker wrote:
> Hi everyone,
>
> I have a Postgres 9.3.3 database machine. Due to some intelligent work on
> the part of someon
On Mar 27, 2014, at 5:29 AM, Michael Paquier wrote:
> On Thu, Mar 27, 2014 at 1:42 AM, Steven Schlansker
> wrote:
>>
>> On Mar 25, 2014, at 7:58 PM, Adrian Klaver wrote:
>>>>
>>> Yea, vacuum just marks space as available for reuse it does not actua
On Apr 2, 2014, at 3:08 PM, Jacob Scott wrote:
> Hi,
Hello there ;)
>
>
> Does upgrading a a disk being used by postgres (9.1, on Ubuntu) with the
> following process sound safe?
> • pg_start_backup
> • Take a filesystem snapshot (of a volume containing postgres data but
> not
On Apr 16, 2014, at 4:27 PM, Susan Cassidy
wrote:
> Is there any way to let a transaction "see" the inserts that were done
> earlier in the transaction? I want to insert a row, then later use it within
> the same transaction.
>
> If not, I will have to commit after each insert, and I don't
>> On Wed, Apr 16, 2014 at 4:31 PM, Tom Lane wrote:
>> Susan Cassidy writes:
>> > Is there any way to let a transaction "see" the inserts that were done
>> > earlier in the transaction?
>>
>> It works that way automatically, as long as you're talking about separate
>> statements within one tra
27;{-02f6-379d-c000-00026810,-0320-b467-c000-00026810,-000d-cefb-c000-00026810}'::uuid[]))
(16 rows)
Wow! Changing the query from using an OR clause to a UNION DISTINCT with two
SELECTs reduced the cost from 1379485.60 to 3366.35! And the gains are
rea
On Jul 5, 2012, at 3:51 PM, Tom Lane wrote:
> Steven Schlansker writes:
>> Why is using an OR so awful here?
>
> Because the OR stops it from being a join (it possibly needs to return
> some rows that are not in the semijoin of the two tables).
>
>> Why does it
On Jul 5, 2012, at 6:35 PM, Jasen Betts wrote:
> I note you've decided to rewrite this query as a union
>
>> SELECT * FROM account
>> WHERE user_id in
>>(SELECT user_id FROM account
>> WHERE id =
>> ANY('{-02f6-379d-c000-00026810,-0320-b467-c000-00026810,000
On Jul 6, 2012, at 9:24 PM, Gurjeet Singh wrote:
> On Thu, Jul 5, 2012 at 7:16 PM, Steven Schlansker wrote:
>
> On Jul 5, 2012, at 3:51 PM, Tom Lane wrote:
>
> > Steven Schlansker writes:
> >> Why is using an OR so awful here?
> >
> > Because the OR
I'm using Postgres hash indices on a streaming replica master.
As is documented, hash indices are not logged, so the replica does not have
access to them.
I understand that the current wisdom is "don't use hash indices", but
(unfortunately?) I have benchmarks that
show that our particular applic
I think it's pretty easy to show that timestamp+size isn't good enough to do
this 100% reliably.
Imagine that your timestamps have a millisecond resolution. I assume this will
vary based on OS / filesystem, but the point remains the same no matter what
size it is.
You can have multiple writes
It is not possible to compile Postgres contrib/uuid-ossp on the newest release
of Mac OS X, 10.8
The specific compile error:
make -C uuid-ossp install
/bin/sh ../../config/install-sh -c -d '/usr/local/Cellar/postgresql/9.1.3/lib'
/usr/bin/clang -Os -w -pipe -march=native -Qunused-arguments
-I
On Jul 30, 2012, at 7:35 PM, Tom Lane wrote:
> Steven Schlansker writes:
>> It is not possible to compile Postgres contrib/uuid-ossp on the newest
>> release of Mac OS X, 10.8
>
> This looks like some variant of the same issue that OSSP's uuid
> package has had
On Aug 19, 2012, at 8:01 PM, Scott Marlowe wrote:
> On Tue, Jul 10, 2012 at 1:09 AM, Steven Schlansker
> wrote:
>> I'm using Postgres hash indices on a streaming replica master.
>> As is documented, hash indices are not logged, so the replica does not have
>
On Aug 19, 2012, at 2:37 PM, Jeff Davis wrote:
> On Tue, 2012-07-10 at 00:09 -0700, Steven Schlansker wrote:
>> I understand that the current wisdom is "don't use hash indices", but
>> (unfortunately?) I have benchmarks that
>> show that our particular appli
On Aug 23, 2012, at 11:13 AM, "Gauthier, Dave" wrote:
> With \timing set on, I run an update statement and it reports
>
> Time: 0.524 ms
>
> Is that really 0.524 ms? As in 524 nanoseconds?
0.524ms = 524000ns
Perhaps you meant microseconds?
0.524ms = 524us
If all your data happens to
On Nov 16, 2012, at 11:59 AM, Richard Huxton wrote:
> On 16/11/12 19:35, Shaun Thomas wrote:
>> Hey guys,
>>
>> So, we have a pretty beefy system that runs dual X5675's with 72GB of RAM.
>> After our recent upgrade to 9.1, things have been... odd. I managed to track
>> it down to one setting:
52 matches
Mail list logo
