On Oct 3, 2013, at 23:56, Michal TOMA wrote:
> I have a problem on my pg 9.2.4 setup (OpenSuse 12.2, kernel 3.2.13).
> My pg_xlog directory is growing uncontrolably untill it fills the partition.
> The database is under heavy write load and is spread on two tablesapces one
> on a ssd software r
Rafael B.C. wrote:
> I am dealing with the old decision about hiw to store data objects and trying
> to understand deep the
> postgre system including toast, pg-largedataobject table and so on.
>
> My real doubt right now is why bytea does not gets processed by toast system
> even when is grow e
On 10/3/2013 2:22 AM, Rafael B.C. wrote:
My real doubt right now is why bytea does not gets processed by toast
system even when is grow enough. Since ive read that tuples are not
allowed to expand over several dtabase pages.
a tuple can't expand over ONE database page, and generally it prefers
A 2013-10-03 17:50, Alvaro Herrera escrigué:
Giuseppe Broccolo wrote:
The format of the script file has to be one SQL command per line;
multiline SQL commands are not supported, and empty lines are
ignored. This could bring to errors. Could this be your case?
Multiline SQL commands are not su
Hello Alban,
Yes I think I'm saturating the HDD IO but the problem is that the only thing
that runs on that server is postgres itself.
I have two tablespeces one on a SSD software raid 1 another one on a HDD
software raid 1.
The disk which is saturating is the HDD and the pg_xlog directory is on
Hey short trick :
to avoid to use the schema name multiple time (more readable and more easy
to re use).
You can use the
SET search_path gpstracking_device_tracks, public;
(see manual here :
http://www.postgresql.org/docs/current/static/sql-set.html)
Cheers,
Rémi-C
2013/10/2 Carlos Eduardo Sot
Hello.
I have a noob question about table aliases in SQL.
Suppose the following query:
SELECT *
FROM deal
WHERE
deal.id IN (
SELECT DISTINCT deal.id
FROM
deal
JOIN partner_share ON deal.id = partner_share.deal_id
JOIN partner ONshare.partne
I almost always alias my tables by default with something short (Usually 1
- 3 characters), but not my subselects for an in list. In this case I
would do d1, d2, ps, and p for the different tables. I then do my best to
use the same alias in all my queries. I am also big on formatting the SQL
h
Ladislav Lenart wrote
> * Should I alias one of the references to deal?
> * The above query works the same both with and without an alias, so is it
> simply
> a matter of taste / good practice?
> * Where can I find more info about this, i.e. when the alias is mandatory
> and
> when it is only a con
On 4.10.2013 15:11, David Johnston wrote:
> Ladislav Lenart wrote
>> * Should I alias one of the references to deal?
>> * The above query works the same both with and without an alias, so is it
>> simply
>> a matter of taste / good practice?
>> * Where can I find more info about this, i.e. when the
I *know* that without an ORDER BY clause, the database is free to reorder
results in any way it likes. However, I recently ran into a case where the
*SAME* query was returning results in a different order *within* a single
transaction, which surprised me (we fixed it by adding the missing ORDER
Evan Jones wrote:
> I *know* that without an ORDER BY clause, the database is free to reorder
> results in any way it likes. However, I recently ran into a case where the
> *SAME* query was returning results in a different order *within* a single
> transaction, which surprised me (we fixed it by
On Oct 4, 2013, at 13:03 , Kevin Grittner wrote:
> That is not a valid assumption. For one thing, the default
> transaction isolation level is read committed, and at that
> isolation level you are not guaranteed to even get the same *rows*
> running the same query twice within the same transactio
Evan Jones wrote:
> I *know* that without an ORDER BY clause, the database is free to
> reorder results in any way it likes. However, I recently ran into a
> case where the *SAME* query was returning results in a different order
> *within* a single transaction, which surprised me (we fixed it by
>
14 matches
Mail list logo
