On Tue, May 26, 2015 at 3:07 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
Realistically, with merge.conflictstyle = diff3 (why is this not the
default?), resolving whitespace conflicts that occur when you try to
cherry-pick is typically not very
happening on
slow storage, can you not just adjust the kernel vm.dirty* tunables to
start making the kernel write out dirty buffers much sooner instead of
letting them accumulate until fsyncs force them out all at once?
a.
--
Aidan Van Dyk Create like
it.
Or if someone wants to fix it properly of course :)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca
verifies what kind
of line endings are in a file. Could maybe be as simple as checking
the size of the file?
This leads to making sure you keep your verification list in source,
and up-to-date too...
a.
--
Aidan Van Dyk Create like a god,
ai
PQconnectdb...
But if they are decoupled, I could easily envision an app that
pauses it's use of the backend to allow some other libpq access to
it for a period.
You'd have to trust whatever else you let talk on the FD to the
backend, but it might be useful...
--
Aidan Van Dyk
://www.postgresql.org/mailpref/pgsql-hackers
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
--
Sent via pgsql-hackers
On Sep 4, 2012 6:06 PM, Andrew Dunstan and...@dunslane.net wrote:
Frankly, I have had enough failures of parallel make that I think doing
this would generate a significant number of non-repeatable failures (I had
one just the other day that took three invocations of make to get right).
So I'm
mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http
guaranteed version of it.
But that fine line is actually a difficult (impossible?) one to define
if you don't know, at the moment of decision, what the next few
moments will/could become.
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca
the commit
message due to server crash, network disconnect, client middle-tier
crash, etc).
So people are already susceptible to that, and defending against it, no? ;-)
And they are susceptible to that if they are on PostgreSQL, Oracle, MS
SQL, DB2, etc.
a.
--
Aidan Van Dyk
good enough for us ;-)
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
--
Sent via pgsql-hackers mailing
open-source projects.
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
--
Sent via pgsql-hackers mailing
using operators, what would you think is an
appropriate name for the file the operator is dumped into?
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca
) and a sane, simple filename, than have
every function in every database in a separate file with some strange
mess in the filename that makes me cringe every time I see it.
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca
visible...
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
--
Sent via pgsql-hackers mailing list (pgsql
and 100s of GB of data
in my pg directory, the *only* corruption is that a single file
pg_control file is missing?
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca
mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http
it
know to *not* apply it again?
The lsn of the change.
So why isn't the LSN good enough for when C propagates the change back to A?
Why does A need more information than C?
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca
On Wed, Jun 20, 2012 at 3:49 PM, Andres Freund and...@2ndquadrant.com wrote:
On Wednesday, June 20, 2012 09:41:03 PM Aidan Van Dyk wrote:
On Wed, Jun 20, 2012 at 3:27 PM, Andres Freund and...@2ndquadrant.com
wrote:
OK, so in this case, I still don't see how the origin_id is even
enough
processing on the remote...
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
--
Sent via pgsql-hackers mailing
remote_write
remote_sync
it is much more clear...
With a single remote_write, you can't tell just by itself it that is
intended to be it's a write *to* the remote, or it's a write *by*
the remote. But when combined with other terms, only one makes sense
in all cases.
--
Aidan Van Dyk
/setof in core, I
could see this being a very nice RPC mechanism for PostgreSQL.
Plain HTTP still give's you the session/transaction control problem of
stateless clients, but maybe coupled with PgPool you could cobble
something together...
a.
--
Aidan Van Dyk
time as backends double-write dirty buffers.
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
--
Sent via
accumulated to make sure it's writes were
consistent. Exactly as the master would do.
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca
the hint-bit-write penalty too...
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
--
Sent via pgsql-hackers
On Fri, Jan 6, 2012 at 6:48 PM, Aidan Van Dyk ai...@highrise.ca wrote:
I think I've said it before, but I'm guessing OLTP style database
rarely have pages written that are dirty that aren't covered by real
changes (so have the FPW anyways) and OLAP type generally freeze after
loads to avoid
better, is there a way we could start injecting notify events
into the cluster on these types of changes? Especially now that
notify events can take payloads, it means I don't have to keep
constantly polling the database to see if it things its connected,
etc.
a.
--
Aidan Van Dyk
mere two weeks ago ...
Generally when I've wanted these things, I just make a new $HOME in
my shared user home dir:
export HOME=$HOME/aidan
It's worked for things I've wanted, I haven't tried it for psql stuff
a.
--
Aidan Van Dyk Create like a god
And the problem that optimization introduces:
1) Since they aren't guarenteed durable, we can't believe a checksum
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca
.
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
--
Sent via pgsql-hackers mailing list (pgsql-hackers
it dirty), a page that was
really messed up on the kernel panic that last happened causing this
whole mess, or an even older page that really is giving bitrot...
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca
they are bogus... And to make matters worse, we don't even
know when the perioud of they may be bugus ends, unless we have a
way to methodically force PG through ever buffer in the database after
the crash... And then that makes them very hard to consider
useful...
a.
--
Aidan Van Dyk
at the location it's trying to
read from, because clog hasn't been extended yet by recovery.
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca
On Wed, Oct 26, 2011 at 9:57 AM, Florian Pflug f...@phlo.org wrote:
On Oct26, 2011, at 15:12 , Simon Riggs wrote:
On Wed, Oct 26, 2011 at 12:54 PM, Aidan Van Dyk ai...@highrise.ca wrote:
The read fails because their is no data at the location it's trying to
read from, because clog hasn't been
(both ways, saving IO, or causing lots of random IO)
Can we hope that if pages are not in shared buffers, they are not
recently modified, so hopefully both all visible, and have the VM
bit?set? Or does the table-based nature of vacuum mean there is no
value there?
--
Aidan Van Dyk
scroll offscreen due to errors...
Decorate them with a marker like:
\extension name version
And make the CREATE EXTENSION skip (or verify) it?
It will make psql stop on the \extension command.
a.
--
Aidan Van Dyk Create like a god,
ai
that had data_directory set in it.
Anything else, and I say it's responsibility of whoever scripted the
startup to be able to provide all the necessary information to
pg_upgrade (be it by extra command line options, or crafting a special
pg_data with symlinks that is more normal).
a.
--
Aidan Van Dyk
page that wasn't guarenteed to exists at the start of the
backup period, and bombing out before recovery has a chance to start
replaying WAL and write the new clog page.
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca
options). But because of the
different caught up action, are different features.
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca
On Wed, Sep 21, 2011 at 1:34 PM, Aidan Van Dyk ai...@highrise.ca wrote:
And I think Tom touched on this point in the
recovery.conf/recovery.done thread a bit too.
Doh! That's this thread
/me slinks away, ashamed for not even taking a close look at the to/cc list...
--
Aidan Van Dyk
apps,
mostly odbc), and be able to have the same userid for different
databases, using different settings...
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca
for
code to do:
if (pg_write_no_intr(...) 0)
...
which will only catch some of the errors, and happily continue with the rest...
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http
Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
like omniptr, or ptrtools, walmgr, etc...
Neither of those cases should ever happen. If you're copying a file
into the archive, and making it appear non-atomically in your archive,
your doing something wrong.
Period.
No excuses.
a.
--
Aidan Van Dyk
they've finally remove the BKL out of VFS/inode?
I mean, complaining about scalability in linux 2.6.18 is like
complaining about scalability in postgresql 8.2 ;-)
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca
better to be
able to pick partitions for queries, unless the query is an exact key
= type of operation.
So I'm failing to see the benefit of that key based partitioning,
even if that key-based function was something like date_trunc on a
timestamp...
a.
--
Aidan Van Dyk
Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
might not bother to even start.
It's a double-edged sword. If nobody writes anything, because
everyone is afraid to possibly having to change things, nothing will
never need to be changed ;-)
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca
.
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
--
Sent via pgsql-hackers mailing list (pgsql-hackers
the same
2) Discipline of all new published commits being pgindent clean.
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work
catalog-wise that you need to
manage for upgrades.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
--
Sent via
to be to declare things as:
typedef struct foo { ... } foo;
Is there any reason why we see any struct foo in the sources other
than in the typedef line?
Legacy and invasive patch are good enough reasons, if they are it...
a.
--
Aidan Van Dyk Create like
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
--
Sent via pgsql-hackers mailing list (pgsql-hackers
On Tue, Apr 19, 2011 at 1:57 PM, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
Aidan Van Dyk ai...@highrise.ca wrote:
And for the first-hack-that-comes-to-mind, I find my self
pulling out the named fifo trick all the time, and just leaving my
for/loop/if logic in bash writing SQL
?
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
for extension in 9.1 to provide a basic
provides/features for my extension to give, but if that train has
already left the station, I don't have much choice ;-(
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca
those for me for now until 9.2 (or 9.3, 9.3, etc), if only I had
a way to track them with my installed extension ;-) /stop begging
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http
in.
Thoughts?
So you're really looking to make psql use service connection
definitions more easily, not just retrieve the password associated
with the given (maybe defaulted) host:port:database:user, right?
a.
--
Aidan Van Dyk Create like a god,
ai
needed if we are trying to avoid version comparisons and
want to be describing actual dependencies...
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca
can make (or not).
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
--
Sent via pgsql-hackers mailing list
/monitoring are *equally*
important, because they are what give you confidence your data is as
safe as you think it is...
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca
is not successfully
replicated for any reason, including crash, it is rolled back in the master
too. That would require 2PC.
My worry is that the stricter definition is what many people will expect,
without reading the fine print.
They they are either already hosed or already using 2PC.
a.
--
Aidan Van Dyk
On Mon, Mar 7, 2011 at 2:29 PM, Aidan Van Dyk ai...@highrise.ca wrote:
They they are either already hosed or already using 2PC.
Sorry, to expand on my all too brief comment, even *without*
replication, they are hosed.
Once you issue commit, you have know knowledge if the commit is
durable
with errors during the installation.
And make sure you don't try and drop pl/pgsql language when
the extension is installed either.
Maybe that's enough for 9.1.
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca
with them ;-)
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
--
Sent via pgsql-hackers mailing list (pgsql
, and at that point, *I* don't need multiple
versions of it anymore. I'm going to keep the same extension
objects/libraries backwards compatible, and I just need a way to tell
PG to run something after I've replaced the shared libraries to
perform any upgrade tweeks.
a.
--
Aidan Van Dyk
to test somethign else. And not have to upgrade my slony 2
instance just to get the critical bugfix for my production slony
1.2$x+1.
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http
to release
ist o make a single release of all versions.
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
--
Sent
.
Personally, I'ld rather be able to install the *same*
extension/version in different schemas at the same time then move an
extension from 1 schema to another, although I have no problems with
extensions moving out under a function's foot (just like loose
objects).
a.
--
Aidan Van Dyk
.
With having the $old - $new scripts, the new .so only needs to have
functions enough that the DROPs work, and the new CREATE... work.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http
-initiated WAL unless there is a sync slave connected. Yes, I
understand that leads to hard-fail, and yes, I understand I'm in the
minority, maybe almost singular in that desire.
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca
On Fri, Jan 21, 2011 at 1:03 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Fri, Jan 21, 2011 at 12:23 PM, Aidan Van Dyk ai...@highrise.ca wrote:
When no sync slave is connected, yes, I want to stop things hard.
What you're proposing is to fail things
that waiting/error still only happens at the COMMIT
statement from the client.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like
what I might be
looking at, so conversion is easy...
But then again, I don't have multiple gigabytes of logs to process either.
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http
to not need as many file handles, and
clients reading the fifo would notice when the writer (postmaster)
closes it.
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca
representation smaller
- Making COPY more efficient
As far as I know, none of this work is public yet.
pg_dump is another story. But it's not related to base backups for
PIT Recovery/Replication.
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca
. I'll take
it over nothing ;-)
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
--
Sent via pgsql-hackers
or
newer. But no chance of older.
But personally, I'm not interested in that ;-)
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work
(as long as streamrecv
is running), and my verifyarchive command would make sure that if
for some reason, the backup archive went down, the wal segments
would be blocked on the master until it's up again and current.
a.
--
Aidan Van Dyk Create like a god
might be committed, even
though you didn't get the commit packet, and when your DB recovers,
it's got the committed data that you never knew was committed.
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca
On Wed, Dec 29, 2010 at 2:27 AM, Joel Jacobson j...@gluefinance.com wrote:
description of split stuff
So, how different (or not) is this to the directory format that was
coming out of the desire of a parallel pg_dump?
a.
--
Aidan Van Dyk Create like
On Wed, Dec 29, 2010 at 9:11 AM, Gurjeet Singh singh.gurj...@gmail.com wrote:
On Wed, Dec 29, 2010 at 8:31 AM, Joel Jacobson j...@gluefinance.com wrote:
2010/12/29 Aidan Van Dyk ai...@highrise.ca
On Wed, Dec 29, 2010 at 2:27 AM, Joel Jacobson j...@gluefinance.com
wrote:
description
in the database. And path has to be encoding aware.
And you want names that glob well, so for instance, you could exclude
*.data (or a schema) from the diff.
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca
search the bugtracker is no less rude than search the archives...
And most of the bugtrackers I've had to search have way *less*
ease-of-use for searching than a good mailing list archive (I tend to
keep going back to gmane's search)
a.
--
Aidan Van Dyk
.
Being able to arbitrary (i.e at any point in time) prove that the
shared buffers contents are exactly what they should be may be a
worthy goal, but that's many orders of magnitude more difficult than
verifying that the bytes we read from disk are the ones we wrote to
disk.
a.
--
Aidan Van Dyk
.
But please don't deny the rest of us airbags while you keep working on
teleportation ;-)
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca
behind on
fsyncing/applying it's WAL, but that's good too. At least then the
ACK comes back, and the master knows the slave is still churning away
on the last batch of WAL, and can decide if it wants to think the
slave is too far behind and boot it out.
--
Aidan Van Dyk
script for
every single version is way more than asking me to just specify an
upgrade script for versions.
Again, I'ld love for the version to support some sort of prefix or
wildcard matching, so I could do:
upgrade-1.* = $EXT-upgrade-1.sql
upgrade-2.* = $EXT-upgrade-2.sql
a.
--
Aidan Van
matches.
If only have those 2 lines to manage, it's a lot more likely I won't
mess them up than if I have to manage 30 almost identical lines and
not miss/duplicate a version.
;-)
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca
type match, then the PG versionins woudl work too,
for intsance:
upgrade-9.0.=...
would match any pg 9.0.*
I guess you could use SQL like if that' more consitent...
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca
with different
caches that are incoherent to have those problems.
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like
that won't *necessarily*
force cache coherency in your local lock/variable memory.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca
-coherency stuff in it ;-)
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
--
Sent via pgsql-hackers mailing
, have
users not mis-manage, and make sure users don't mis-use...
So, yes, ident is only as secure as the *network and machines* it's
used on. Passwords are only as secure as the users managing them, and
the machines/filesystems containing .pgpass ;-)
a.
--
Aidan Van Dyk
and
rebuild-able.
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
--
Sent via pgsql-hackers mailing list
being too slow
;-)
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
--
Sent via pgsql-hackers mailing list
.
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
--
Sent via pgsql-hackers mailing list (pgsql-hackers
of it, so the torn-page checksum is fixed
Both of these are theoretical performance tradeoffs. How badly do we
want to verify on read that it is *exactly* what we thought we wrote?
a.
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca
the
tables...
/waving hands
--
Aidan Van Dyk Create like a god,
ai...@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
--
Sent via pgsql-hackers mailing
1 - 100 of 363 matches
Mail list logo