#x27;t really see trusting Postgres on a filesystem that felt free to
compress portions of it. Would the filesystem still be able to guarantee that
torn pages won't "tear" across adjacent blocks? What about torn pages that
included hint bits being set?
--
Gregory Stark
Enterpris
and SIGQUIT I wonder if it's
(erroneously?) ignoring SIGWINCH as well.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to y
"Scott Marlowe" <[EMAIL PROTECTED]> writes:
> On Thu, Oct 30, 2008 at 4:41 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
>> "Scott Marlowe" <[EMAIL PROTECTED]> writes:
>>> On Thu, Oct 30, 2008 at 4:01 PM, Gregory Stark <[EMAIL PROTECTED]> wr
e set of database blocks
within the filesystem block is written.
The only way I could see this working is if you use a filesystem which logs
data changes like ZFS or ext3 with data=journal. Even then you have to be very
careful to make the filesystem block size that the journal treats as atomic
m
Ivan Sergio Borgonovo <[EMAIL PROTECTED]> writes:
> On Fri, 31 Oct 2008 08:49:56 +
> Gregory Stark <[EMAIL PROTECTED]> wrote:
>
>> Invisible under normal operation sure, but when something fails the
>> consequences will surely be different and I can't
data=journal might also be ok. These both have to make performance
sacrifices to get there though.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.o
beat any combination of RAID-0 and RAID-1 with the same
number of drives at read performance. It's advantage is that you get more
capacity.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
--
Sent via pgsql-general
to post those via
> http://explain-analyze.info/
What would be really neat would be having the mailing list do something
automatically. Either fix the message inline or generate a link to something
like this.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me abou
's hard to follow
because we've been picking up more simultaneous threads instead of all being
on one thread together before moving on to the next one.
Another idea, I wonder if the project has gone more international and
therefore has more traffic at odd hours of the day for everyone. I
Craig Ringer <[EMAIL PROTECTED]> writes:
> Gregory Stark wrote:
>> Another idea, I wonder if the project has gone more international and
>> therefore has more traffic at odd hours of the day for everyone. It would
>> also
>> mean more long-lived threads with lar
x
From:
http://www.postgresql.org/docs/8.3/interactive/monitoring-stats.html
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL
training!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
poorly because of the
time spent sifting through all that dead space.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes
d > will behave quite differently.
That's why the casts disappeared -- you probably weren't running the queries
you thought you were running in 8.2 and previously.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me abou
it is how much dead space is in the table due
to previous updates and deletes, as well as how fragmented the indexes have
become over time.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
--
Sent via pgsql-general maili
e warnings for each list they're not on.
> (If you want it to be even more pain-free, add a Reply-To:
> pgsql-advocacy header or some such.)
Yeah, actually that doesn't work.
If you want to do that the only way to do it properly is to Bcc the various
lists with the To set to the
Alvaro Herrera writes:
> Gregory Stark wrote:
>> Alvaro Herrera writes:
>>
>> Well cross-posting is especially annoying on subscriber-only moderated lists
>> such as ours. Anyone who follows up to an email who isn't subscribed to all
>> the lists will get
.
I suspect others already suggested this, but you might look at partial
indexes. If your queries are very dynamic against relatively static data you
might look at building denormalized caches of the precalculated data.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me a
'Y' THEN superman
Which will make Postgres build stats for the result of that expression
specifically. Then if you use that expression exactly as-is in the query the
planner should those statistics. I think. I haven't tried this... Tell us how
it goes :)
I wonder if we should look at b
o respond on-list or if you prefer in personal emails. I do intend
to use the ideas you give in my presentation so mark anything you wouldn't be
happy to see in a slide at a conference some day.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about Enterpr
nsigned char like you had it originally.
What really boggles me is why you don't just use unsigned chars everywhere and
remove all of these casts. or would that just move the casts to strcmp and
company?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about Ent
Gregory Stark writes:
> Teodor Sigaev writes:
>
>> I reproduced the bug with a help of Grzegorz's point for 64-bit box. So,
>> patch
>> is attached and I'm going to commit it
> ...
>
>> !Conf->flagval[(unsigned int) *s] = (unsigned char) val
Tom Lane writes:
> Gregory Stark writes:
>> Maybe I'm missing something but I don't understand how this fixes the
>> problem.
>> s is a "char*" so type punning it to an unsigned char * before dereferencing
>> it is really the same as casting it
ote!
This may not be so timely any more, though I suppose there's always someone
somewhere holding elections :)
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
--
Sent via pgsql-general mailing list (pgsql-genera
this the other day.
I'm kind of wondering what behaviour you two are looking for and what
"different DBMS" you're referring to.
I'm assuming it's not the ANSI fold-to-uppercase behaviour you're looking for.
--
Gregory Stark
EnterpriseDB http://www.
best if we limited ourselves right now to discussing the
problems themselves and not debating the pros and cons of possible solutions.
I want to encourage people to post their peeves even if they know perfectly
well the reasons why things are the way they are.
--
Gregory Stark
Enterpr
that Perl has to really make it a big success though.
Making modules more, uh, modular, so they can be installed and uninstalled
smoothly and preferably without special access privileges is a recognized
issue though.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me
users then there's a convenience
type called regclass which you can use by doing "SELECT conrelid::regclass
from pg_constraint". There are similar regtype and a few others like it too.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about Enterprise
t the hierarchical query ability you're looking for or pivot?
The former we are actually getting in 8.4.
AFAIK even in systems with pivot you still have to declare a fixed list of
columns in advance anyways. Do you see a system where it works differently?
--
Gregory Stark
EnterpriseDB
ave a subquery which executed for every record and retrieved the set of data
to aggregate.
8.4 Will have OLAP Window functions which can implement things like moving
averages.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about Enterp
"Daniel Verite" writes:
> Gregory Stark wrote:
>
>> Is it the hierarchical query ability you're looking for or pivot?
>> The former we are actually getting in 8.4.
>>
>> AFAIK even in systems with pivot you still have to
>> declare a
former would indeed be a
package bug.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ovements and HOT previously and the free space map in 8.4 the
situation will be much improved. However there are still some common usage
patterns where people run into problems.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production
other
> checking if a perl module exists in debian I just do
> perl -MCPAN -e 'install (DBD::Pg)' or whatever pkg
Ah, well that's not a mistake, but you need to check what -dev packages the
CPAN module you're building requires.
--
Gregory Stark
EnterpriseDB
lue though.
> I understand the Hash is not recommended. When should I use the Gin index ?
GIN and GIST are used for fairly specialized purposes. Full text searching,
geometric data types, etc.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB
d the DBMS should not worry about providing the
> information about the columns, maybe by simply not allowing the
> dynamic-column ones in subqueries.
What about a WHERE clause like
WHERE P1 > P2
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB
ull_listing values contain "view"? How
does it perform with much more selective searches?
If your full_listing values are quite large then recalculating the tsvector
might be a lot more expensive than doing a full table scan and LIKE match for
cases when nearly the whole table is
ally have to store the extra
column.
Note that in this example if you were to search on just age it wouldn't be
able to use either of these indexes however. In theory it could use the
indexes if you search on just gender but it would be unlikely to for all the
same reasons as previo
ce base which is flexible enough to extend to
use a database backend. I'm under the impression most cron daemons are based
on pretty old and ossified source bases and are burdened by a lot of legacy
compatibility requirements.
--
Gregory Stark
EnterpriseDB http://www.enterpr
less i/o impact. The defaults process only a few
kilobytes before sleeping which probably cause a lot of random seeks. If you
multiple both by 10 then you'll process close to a megabyte of data and then
sleep for a long while. Just a thought -- I haven't tried this on a test box.)
--
The more normal suggestion is to increase *vacuum_cost_delay* which tells it
to sleep longer between bits of work. Don't increase it too much or vacuum
will take forever. But if you increase it from 20 to 40 it should use half as
much i/o as bandwidth as now.
--
Gregory St
ould stop holding our noses and do something about
> this old gotcha. That type's not going away anytime soon, but could we
> rename it to char1 or something like that?
int1?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's S
ank() over (partition by charge order by
coldspot_time desc) as r) where r = 1
?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make chang
d about reopening it, but while I don't think the current
logic is right I don't think wrapping to 80 columns when your terminal is
wider is one of the current broken cases. It tends to fail in the opposite
direction of randomly not wrapping at all so it's kind of surprising
able scan would be more efficient than any index.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
put a timestamp column on your tables and manage the date
you put in their according to a policy you control.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
--
Sent via pgsql-general mailing list (pgsql-general@postgr
Richard Broersma writes:
> On Wed, Feb 25, 2009 at 5:21 AM, Gregory Stark wrote:
>
>> I'm not sure using xmin is such a great idea really. It's handy for ad-hoc
>> queries but there are all kinds of cases where it might not give you the
>> results you expect
e. Needing
two cracks at describing the problem is pretty much par for the course here.
I haven't tested the query to see what's going on but if the problem is due to
random() then in 8.4 you could use WITH to guarantee that the subquery is
executed precisely once and the results reuse
length
of time while holding locks which block other transactions that's bad.
Alternately if you see a query in pg_stat_transaction which is taking a long
time to run you might check whether you have a bad plan or a bad query running
while holding locks effectively doing the same thing.
--
Greg
from the Default
timezone_abbreviations file.
SELECT '2009-01-01 00:56:00 Indian/Mauritius'::timestamp with time zone;
timestamptz
2008-12-31 19:56:00+00
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ting as a client. That lets you stop/start transactions
freely. It also allows you to open multiple connections or run the client-side
code on a separate machine which can have different resources available.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about
disk sort of all the records picked from raw_data.
It does seem much more likely that whatever index you have it using on
timestmp or item_name or some_data_field is sometimes being used and sometimes
not. Perhaps it's switching from an index on one of those columns to an index
on some other c
;-)
>
> However, a tip that might help is that there should be more information
> about the problem in the postmaster log. We intentionally don't send
> details about the conf file's contents to the client...
Perhaps we should send a HINT to the client saying to cons
do it once and only because I had a filesystem
corruption.
> I'll try Debian lists / irc - hopefully don't get snarks. :)
Yes well...
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Emanuel Calvo Franco writes:
> 2009/3/10 Gregory Stark :
>> Tom Lane writes:
>>> However, a tip that might help is that there should be more information
>>> about the problem in the postmaster log. We intentionally don't send
>>> details abo
should be released sometime in the
next 3-6 months and will allow you to have a different encoding and locale for
each database.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
--
Sent via pgsql-general mailing
ing about "very large" at about 4-10 TB.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
-
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
something like
creation_date <= now() -
Both because of the now() instead of 'now'::date and because the latter is a
comparison that can be indexed instead of an expression which could use an
index on creation_date.
--
Gregory Stark
EnterpriseDB http://www.enterp
than it
saves in the query -- the reason these limits exist at all..
geqo_threshold
join_collapse_limit
from_collapse_limit
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
-
Sent via pgsql-general mailing
just as good as the existing code. Just use regular gettext on the two strings
separately and pick the right one based on the English rule.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
--
Sent via pgsql-gen
that's a secondary issue to getting it on the
> TODO list, which is all I'm suggesting at present.
Well I think we need to be clear enough at least on the "what" if not the
"how". But there's a bit a of a fuzzy line between them I admit.
--
Gregory Stark
E
a) (sfunc = magic_transition, stype = a);
Not sure it'll be faster though.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To m
.
If there's any sequential i/o mixed in then yeah, it's pretty poor.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make chang
both cases? I suspect what's happening is that the
planner is estimating it will need 2G to has all the values and in fact it
would need >8G. So for values under 2G it uses a sort and not a hash at all,
for values over 2G it's trying to use a hash and failing.
--
Gregory Stark
Ent
[EMAIL PROTECTED] writes:
> At a customer site, we've made a migration from Oracle 8.1.5 to PGSQL
> 8.1.1. The migration happened without any problem and now the performances
> are better with PG than with Ora, but the customer noticed that the size
> of PG on disk where much greater than the siz
to be using USR1/USR2 or other
signals that library routines won't think they have any business rearranging.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> Sure, but it might be getting delivered to, say, your "sleep" command. You
>> haven't checked the return value of sleep to handle any errors that may
>>
may, I
haven't thought it through. Nor have I thought through whether it would be
possible to keep the original name.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
ou would be removing substantially less, and once you get to about 10%
then you're back where you started.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
rformance impact in absolute
terms. I'm much more interested in changing the performance characteristics so
they're predictable and scalable. It doesn't matter much if your 1kb table is
100% slower than necessary but it does matter if your 1TB table needs 1,000x
as much vacuumi
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Greg Stark: WITH/Recursive Queries?
Uhm, I posted two weeks ago saying I had to shelve that temporarily.
On the other hand I've submitted a patch to reduce the storage overhead of
varlenas under 128 bytes by 3-7 bytes ea
"Gregory Stark" <[EMAIL PROTECTED]> writes:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
>
>> Greg Stark: WITH/Recursive Queries?
>
> Uhm, I posted two weeks ago saying I had to shelve that temporarily.
>
> On the other hand I've s
ow that I have some time. If not then what am I
misunderstanding about the pstate and where would be the right place to keep
this kind of parser namespace state?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)--
value | value
---+---
one |
two | two
three | three
(3 rows)
"USING" would work too but then you only get one output column rather than two
which is not so helpful in this case.
postgres=# SELECT *
FROM (VALUES ('one'),('two'),('
'examine'),('three')) AS foo(token)
LEFT OUTER JOIN tokens USING (token)
WHERE u.user_idx = 15;
Note that your query is joining 6 tables and there are two joins that don't
have any join constraint on them. So you're getting the cartesian product of
those jo
nversation ... LIMIT 10)
I think your timing results are being dominated by the overhead it takes to
actually measure the time spent in each node. With the limit node it has to
call gettimeofday nearly twice as often. That works out to about 2.5us per
gettimeofday which seems about right
Is this known? If you create a table with a SERIAL and then rename the table
you can't dump/restore the database. The create table creates a sequence based
on the new table name but the setval() call still refers to the old sequence
name.
I'm not really sure which sequence name ought to be used.
ommitted
transactions are affected by other transactions when they commit. In this case
the uncommitted LISTEN is not being affected by the committed NOTIFY.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)--
mantics for the
outermost transaction and isn't actually committed until the outer transaction
commits.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
#x27;re basically skipping a single tree level in favour of earlier query
planning which is probably not going to be noticeable.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
it will
> consider using nonconsecutive index columns
Really? Is this the "skip scan" plan people were pining for? I missed when
that happened.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)--
Tom Lane <[EMAIL PROTECTED]> writes:
> Martijn van Oosterhout writes:
> > The main thing I want to use them for is for cumulative output.
> > ...
> > With window functions you define for each row a "window" which is from
> > the beginning of the table to that row and then sum the values, for
> >
Tom Lane <[EMAIL PROTECTED]> writes:
> If this is a common result from short-lived
> network problems then you have a beef with the TCP stack at one end
> or the other ... TCP is supposed to be more robust than that.
Or a beef with some firewall or router along the way. NAT routers are
particular
Jim Bryan <[EMAIL PROTECTED]> writes:
> "/home/jb/Desktop/DateTimeData.txt" for reading:
> Permission denied
>
> -rw-rw-r-- 1 jb jb 83 Aug 25 14:30
> DateTimeData.txt
I suspect it doesn't have "x" permission on some parent directory, what does
ls -ld /home /hoome/jb /home/jb/Desktop
I guess Tom fixed some bugs when he reimplemented NUMERIC a while back.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 6: explain analyze is your friend
Tom Lane <[EMAIL PROTECTED]> writes:
> Bruce and some other people thought this was confusing, so it's been
> changed for 8.2.
No kidding. They confused me.
Well Thanks for the explanation,
The new messages are infinitely clearer
--
greg
---(end of broadcast)
301 - 385 of 385 matches
Mail list logo