I saw this:
http://blog.pgaddict.com/posts/postgresql-on-ssd-4kb-or-8kB-pages
It made me wonder: if SSDs have 4kB/8kB sectors, and we'd make the Postgres
page size equal to the SSD page size, do we still need full_page_writes?
Regards
Marcin Mańk
ension to the SQL
standard):
select distinct on(x) x, y, z
from the_table
order by x, z
Regards
Marcin Mańk
On Thu, Oct 3, 2013 at 11:56 PM, Michal TOMA wrote:
>
> Now I have:
> checkpoint_completion_target = 0.9
> wal_buffers = 8MB
> checkpoint_segments = 16
> checkpoint_timeout = 20min
> shared_buffers = 2GB
> log_checkpoints = on
>
> This is what I can
x27;m having some trouble
> getting this done.
>
Is it crashing on a specific database object? pg_restore -v will tell you
how far it went. Then try to restore only that object. Is it perhaps
crashing on a specific row?
Try producing a self contained test case (like only the culprit table,
anonymized).
Regards
Marcin Mańk
Dnia 9 lip 2013 o godz. 00:46 Michael Paquier
napisał(a):
> On Tue, Jul 9, 2013 at 5:04 AM, Robert James wrote:
>> On 7/8/13, hubert depesz lubaczewski wrote:
>>> On Mon, Jul 08, 2013 at 09:09:26AM -0400, Robert James wrote:
I have two relations, where each relation has two fields, one
I just tried make uninstall. I did:
sudo make uninstall
which goes:
make -C doc uninstall
make -C src uninstall
make -C sgml uninstall
rm -f '/opt/local/share/doc//postgresql/html/'*
'/opt/local/share/man'/man1/* '/opt/local/share/man'/man3/*
'/opt/local/share/man'/man7/*
/bin/sh: /bin/rm: Argume
inking there. Is this actually needed /
not dangerous?
Greetings
Marcin Mańk
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
I privately pointed Martin Pitt (Debian maintainer) to this
discussion, his response below.
Martin, I believe what happened is:
the original complainer did /etc/init.d/postgresql restart
this called pg_ctlcluster --force restart
this effectively did: pg_ctlcluster --force stop (which removed the
p
On Tue, Jul 24, 2012 at 3:16 AM, Craig Ringer wrote:
> It shouldn't matter - only PostgreSQL was restarted, not the whole machine
>> - and cleanly at that. Very strange.
>
>
> look at pg_ctlcluster, (which does the restart):
if (!fork()) {
close STDOUT;
exec $pg_
On Tue, Jul 10, 2012 at 10:06 PM, Jeff Ross wrote:
> 2012-06-19 15:37:36.283752500 LOG: statement: update
> survey_response set srv_resp_submitted = now() where srv_resp_srv_id = 2
> and srv_resp_pp_id = 25399
>
> jross@wykids localhost# select * from survey_response where
> srv_resp_submitted
On Tue, Nov 29, 2011 at 7:21 PM, Tyler Hains wrote:
> # explain analyze select * from cards where card_set_id=2850 order by
> card_id limit 1;
> QUERY PLAN
> -
select (ts_parse('default','the quick brown fox jumped over the lazy
fox')).token
Greetings
Marcin Mańk
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
o.)
>
"alter role set statement_timeout" solves my immediate problem (I did not
know about it, thanks guys). Maybe a comment in postgresql.conf, or docs:
# note: statement_timeout applies to autovacuum, pg_dump, vacuumdb etc.
# If you set it globally, consider "alter role postgres set
stat
issue. and vacuumdb. This is
all on 8.1.4 .
Yeah, system-wide statement_timeout is not much of a brilliant idea :(
Pozdrawiam
Marcin Mańk
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http
14 matches
Mail list logo
