On 11 October 2017 at 08:09, Christophe Pettus wrote:
>
>> On Oct 10, 2017, at 23:54, Simon Riggs wrote:
>>
>> The use case described seems incredibly
>> unreal and certainly amenable to being rewritten.
>
> While it's certainly true that this w
ase.
It isn't "easy" to run the replay process out of memory because
clearly that doesn't happen much, but yes there are some pessimal use
cases that don't work well. The use case described seems incredibly
unreal and certainly amenable to being rewritten.
Backpatching some
willing to try to come up with a
patch (I already have a hacky version running on my local
machine which fixes it for my use case).
Regards
Simon
--
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9
signature.asc
Description: PGP signature
Hello,
I'm using the following minimal ~/.psqlrc:
\pset expanded on
Now when I select rows from a table which are too long to fit the
screen then I get this output:
simon=> table test;
-[
you name tables and columns, keep it generic.
You'll get a precise measurement of whether it works for you. And the
project will get a representative test case that we can understand and
tune for. And if everyone does that we'll get a set of use cases that
will help demonstrate our per
ther big (500M+ records) with
>> 5-7 indexes. Sometimes it takes us 20 hours+ to get table vacuumed and
>> all progress reporting we have for stage 3 is that it is stage 3.
>
> Yes, things could be improved here.
Yes, it seems that VACUUM progress reporting feature is only about
written for Oracle.
Simon
On 21/01/2017 20:09, Stephen Frost wrote:
Simon,
* Simon Windsor (simon.wind...@cornfield.me.uk) wrote:
My employer wants to move from an in house Oracle solution to a
cloud based Postgres system. The system will involve a number of
data loaders running 24x7 feeding
?
Simon
--
Simon Windsor
Eml: simon.wind...@cornfield.me.uk
Tel: 01454 617689
Mob: 0755 197 9733
“There is nothing in the world that some man cannot make a little worse and
sell a little cheaper, and he who considers price only is that man's lawful
prey.”
--
Sent via pgsql-general mailing
Ahh makes sense, thanks for the explanation!
I was assuming USING() clauses were executed in the context of the
owner of the policy, by passing RLS.
2016-12-17 13:18 GMT-05:00 Joe Conway :
> On 12/17/2016 01:01 PM, Simon Charette wrote:
>> Thanks a lot Joe, that seems to work!
>
&g
Thanks a lot Joe, that seems to work!
I suppose this works because PostgreSQL cannot introspect the
get_owner_id procedure to detect it's querying the "accounts" table
and thus doesn't warn about possible infinite recursion?
Simon
2016-12-16 9:36 GMT-05:00 Joe Conway :
>
Hello Charles,
Unfortunately this will only return accounts matching the current_user's name.
I would expect "SET ROLE foo; SELECT name FROM accounts" to return "foo" and
"bar" and not only "foo" like your proposed solution would do.
Simon
20
s"
Is there any way to alter the "account_ownership" policy's USING clause to avoid
this infinite recursion or a way to model my schema to prevent this from
happening?
Thank you for your time,
Simon
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
* Physical streaming replication, built-in from 9.0+
* Logical streaming replication, partially built in from 9.4+ using pglogical
and
* Logical streaming replication, built in from 10.0+ (not yet released)
Performance is much better than rubyrep
--
Simon Riggshttp://www.2ndQua
On 18 October 2016 at 22:06, Tom Lane wrote:
> Simon Riggs writes:
>> On 18 October 2016 at 19:34, Tom Lane wrote:
>>> If you don't want to have an implicit bias towards earlier blocks,
>>> I don't think that either standard tablesample method is really w
t at a random block and a
random item between min and max?
It wasn't ever intended to be biased and bernoulli in particular ought
to have a strict no bias.
Happy to patch if we agree.
--
Simon Riggshttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, T
's a big issue.
--
Simon Riggshttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On 4 October 2016 at 16:34, Aleksander Alekseev
wrote:
> Hello, Simon.
>
> Thanks for you interest to this project!
>
>> Will you be submitting this to core?
>
> I could align ZSON to PostgreSQL code style. I only need to run pgindent
> and write a few comments. Do y
and pull
> requests are welcome too!
Very good. Oleg had mentioned that dictionary compression was being considered.
It would be useful to be able to define compression dictionaries for
many use cases.
Will you be submitting this to core?
--
Simon Riggshttp://www.2ndQuadrant.co
tation is required.
Anybody can come here and discuss new features. Anybody. They just
need to explain their thoughts and produce evidence for their
assertions.
Come on in, database researchers, we're open to rational contributions.
--
Simon Riggshttp://www.2ndQuadrant.com/
On 25 August 2016 at 09:50, Russell Keane wrote:
> We’re fairly convinced the issue lies with the actual storage but I was
> wondering if there is anything within PG that would be affected by the high
> latency and result in corrupt indexes.
Nothing we know of, at this time.
--
Si
e CRC checked, so it may just be a bug, not corruption that
affects multiple servers.
At the moment we know the Startup process died, but we don't know why.
Do you repeatedly get this error?
Please set log_error_verbosity = VERBOSE and rerun
--
Simon Riggshttp://www
cal replication will be in 10.0.
Yes, 10.0 is the next release, due 2017.
--
Simon Riggshttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make
ent design will be submitted for the next release, 10.0.
--
Simon Riggshttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
he truncation logic always kicks in or small tables of less than
16 blocks. It's more forgiving on bigger tables.
Maybe we could defer the truncation on the standby in some cases.
--
Simon Riggshttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA,
em could be fixed by using
> hot_standby_feedback. I have encountered similar problem but it seems
> hot_standby_feedback was not any help in this case:
>
> https://www.postgresql.org/message-id/20130829.164457.863984798767991096.t-ishii%40sraoss.co.jp
There have been various bugs and enhancement
ion.
>
> If it didn’t make 9.6 core, is there plan to include it in 9.7, or may be
> pglogical becomes available on Windows?
>
>
Currently pglogical does not support Windows.
It's free software, so funding for any new features or requirements is
always welcome.
--
Simon R
e that only parts of the table are there.
> Wouldn't it be much more safe to raise an error as soon as the table is
> touched?
>
How would we know that an external agent had deleted the file? What action
should we take if we did notice?
It's a very good thing that we remain flying eve
On 10 April 2016 at 22:48, Dorian Hoxha wrote:
> Postgres-XL has no highavailibility
>
Postgres-XL 9.5 has had lots of additional work put in, HA being one of
those areas.
--
Simon Riggshttp://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Devel
Hi Konstantin,
Is this open source with The PostgreSQL Licence?
Will you be contributing those changes to the BDR project, or is this a
permanent fork of that?
Thanks
--
Simon Riggshttp://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x
and search binary
> documents, e.g. pdf ?
>
> Ah, no. That's not possible
...not possible, Yet.
PostgreSQL grows by adding the features people need and its changing
rapidly.
--
Simon Riggshttp://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
amp() as ctimestamp
> FROM generate_series(1,1000) as id
> )
> SELECT
> *
> FROM
> (SELECT
> id,
> ctimestamp,
> row_number() OVER (ORDER BY ctimestamp) as rownum
> FROM data_cte
> ) as data_withrownumbers
> WHERE
>
t of the doubt.
>
> * When interpreting the words and actions of others, participants
> should always consider the possibility of misunderstandings.
>
+1
--
Simon Riggshttp://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
On 20 January 2016 at 19:05, Kevin Grittner wrote:
> On Wed, Jan 20, 2016 at 12:47 PM, Simon Riggs
> wrote:
> > On 18 January 2016 at 18:02, Joshua D. Drake
> wrote:
>
> >> * We are tolerant of people’s right to have opposing views.
> >>
> >> * Par
ve point 3 entirely. Point 2 is sufficient to limit what
is said.
Who will decide how this code is enacted? Rules imply rulers, so what is
the constitution of the governing body?
--
Simon Riggshttp://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
able in 9.6.
>
BDR 9.4 is currently at v0.9.3. There isn't a BDR 9.5, since we
concentrated on pglogical.
pglogical works with 9.4 and 9.5 and is currently at v1.0
Future detailed planning for BDR and pglogical is happening now; there
definitely will be future versions with increasing PostgreSQL co
wanted and didn't want
to see in the final product. I think those choices were good ones.
Design your applications carefully, understanding the trade-offs between
availability, local access times, serializability and performance.
--
Simon Riggshttp://www.2ndQuadrant.com/
<h
g about this because there is clearly some confusion around
this.
In official docs very small information about how to configure servers.
>
> Could anyone direct me in right way?
>
If anyone would like to contribute better documentation, they are very
welcome to do so.
--
Simon Riggs
On 29 June 2015 at 21:13, Kevin Grittner wrote:
> Simon Riggs wrote:
> > On 17 June 2015 at 13:52, Kevin Grittner wrote:
> >> Filipe Pina wrote:
>
> >>> if drop the foreign key constraint on stuff_ext table there are
> >>> no failures at all…
.
I can't find any mention of serializability concerns in the RI code itself.
AFAIK it would be strange to exclude FK checks from serializability checks,
since they represent a valid observation of an intermediate state.
Mat Views are excluded but I don't understand why that should be the ca
esn't matter
much.
--
Simon Riggshttp://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
ture similar to Oracle
> Parallel queries
> Multi Master Replication
>
> Some of the names I've seen
> Tom Lane
> Robert Haas
> Greg Smith
> Simon Riggs
>
> Please let me know if a meeting is possible. There is another in-house
> meeting April 17th where I wou
On 28 June 2013 17:17, Tom Lane wrote:
> Simon Riggs writes:
> > We claim conformance to the standard on this.
>
> Not really. The fact that we do RI actions via triggers is already not
> what the spec envisions. As an example, it's well known that you can
> subv
of the underlying triggers except by doing
that directly, which doesn't seem that useful.
Should we have a parameter to define precedence of RI checks? We could hoik
out the triggers and execute them last, or leave them as they are,
depending upon the setting.
--
Simon Riggs
to put it, you'd just need an if test to
prevent the row comparison recursing into its component types. That
would be stored on the pg_type catalog table as a boolean attribute,
defaulting to current behaviour.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Dev
me your feedback on how well that works. I'm
not sure there was any intention for people to buy both.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postg
om. Can you explain?
> Are there risks associated with the `pg_ctl
> restart` approach, or is it safe to use?
PostgreSQL supports both, why do you mention just one of them as a
potential risk?
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Sup
So it would be useful to have a non-default option of statement-level
abort for those cases, as an ease of use feature.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@
ELEASE SAVEPOINT that it seems to otherwise do in COMMIT
> TRANSACTION?
Sounds interesting.
Please can you produce a test case that demonstrates this, then post
the SQL file and an output of a run that shows the negative timing?
Thanks
--
Simon Riggs http://www.2ndQuadrant.
received fundings from PostgreSQL Europe (PGEU) and Software in the
> Public Interest (SPI). Thanks a lot to them !
Well done. This is very good.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-gene
On 7 May 2012 09:19, Magnus Hagander wrote:
> On Mon, May 7, 2012 at 10:14 AM, Simon Riggs wrote:
>> On 7 May 2012 09:01, Vincent de Phily
>> wrote:
>>
>>> Would be nice to see it added to the documentation (unless I just didn't
>>> find
>>>
lease submit a patch. That's how it works here.
> As a bonus question, I guess it would be the same if using synchroneous
> replication ?
Yes
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsq
unk, so as you say, slightly ahead of the
master.
The same thing would also happen in case of a crash.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgre
ge collect libpq programs
automatically though.
I think every time I read some libpq code I see an error.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.
On Fri, Apr 27, 2012 at 7:14 AM, leo xu wrote:
> i have one parimary ,two standby. one standby using stream replication
pg_archivecleanup doesn't work with more than one standby feeding from
a single archive
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Dev
even] .
This may of course be because I am ignorant of where to look.
Is this just a problem with this release 9.1.1 [windows 32bit], and would my
solution be to upgrade?
I am a little loath to do this, as this is a production server.
Simon Willett
--
c++; /* this makes c bigger but
On Mar 19, 2012, at 10:59 AM, Welty, Richard wrote:
> i just finished this thread from May of last year, and am wondering if this
> still represents consensus thinking about postgresql deployments in the EC2
> cloud:
>
> http://postgresql.1045698.n5.nabble.com/amazon-ec2-td4368036.html
>
> Yes,
e Oracle example is very similar code in PostgreSQL, except
that you can't issue ROLLBACK and COMMIT. But then you don't need to
because you can do a conditional error or drop through to a commit.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development,
nteger, e date, foreign key (xid,
e) references x (id, d));
which is to locate the valid row within a temporal lookup table.
Neither is possible, as yet.
Or you might want something entirely different?
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x
t; 2x speed increase for SQLite.
> 4x speed increase for PG.
>
> Hope that'll help some of you.
Did you try this? synchronous_commit = off
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql
ently using 8.3 and 8.4.
>
> Is there the possibility that the logs saved in /var/log also contain
> security details?
I suggest you delete them.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent vi
hen make "select * from bigtable where indexed_field = 'somevalue'; work
> 10 times faster than it does today.
>
>
> I think there is also a wish list on the wiki somewhere.
Nice ideas
Those aren't projects we should be giving to summer students. I don't
suppose ma
who choose not to take that route.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
e:
running tests concurrently.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
r and it would be much faster than the time SQLite
produced.
So using PostgreSQL for testing would be both quicker and more
accurate, if you set the tests up right.
The PostgreSQL regression tests are parallelised - if they weren't
we'd produce a lot less work
--
Simon Ri
am. It doesn't, so saying it runs quicker is irrelevant,
surely?
Perhaps just run half the test, that would make it twice as quick and
still just as valid.
If Postgres tests run in ~1 minute, what benefit have you gained from
saving 30 seconds? How often are you running tests?
So please e
cascading replication.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
parent, type_id FROM uuid.master WHERE id = X
UNION
SELECT depth+1, m.id, m.parent, m.type_id
FROM subtree t, uuid.master m
WHERE m.parent = t.id
)
SELECT count(*)
FROM subtree
WHERE type_id = 4;
Add an index on id
--
Simon Riggs http://www.2ndQuadrant.
On Mon, Jan 23, 2012 at 3:13 PM, Stuart Bishop wrote:
> On Mon, Jan 23, 2012 at 9:37 PM, Simon Riggs wrote:
>> On Mon, Jan 23, 2012 at 2:30 PM, Stuart Bishop
>> wrote:
>>> On Sat, Jan 21, 2012 at 3:31 AM, Jerry Richards
>>> wrote:
>>>> Is s
> response time is of concern.
>
> You might want to investigate pgpool-ii. It sits as a proxy between
> the client and the databases, and as queries are executed
> simultaneously, a synchronous replication setup should be just as fast
> as an unreplicated setup.
Can you share your ac
er? If so, you have been a busy bee.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ery command result
should be freed via PQclear when it is no longer needed.
void PQclear(PGresult *res);
You can keep a PGresult object around for as long as you need it;
it does not go away when you issue a new command, nor even if you
close the connection. To get rid of it, you mu
regularly.
Simon
-Original Message-
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of John R Pierce
Sent: 02 January 2012 11:18
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Large Objects and and Vacuum
On 12/30/11 3:54 PM, Sim
f be a
> bug that they're not updated?
It's intentional. You don't need to, nor can you run VACUUM or
ANALYZE, so there is no need to look at those fields.
The stats tables show activity on the standby separately from the
master, which is useful.
--
Simon Riggs
another method of scanning postgres tables, moving active blocks
and releasing store back to the OS?
Failing this, I can see an NFS mount being required.
Simon
Simon Windsor
Eml: <mailto:simon.wind...@cornfield.org.uk> simon.wind...@cornfield.org.uk
Tel: 01454 617689
Mob:
Hi Salah,
This is equivalent:
WITH numbers AS (SELECT 1 AS a, 2 AS b) SELECT a, b, a+b AS c FROM numbers;
S
On Wed, Dec 21, 2011 at 11:39 AM, salah jubeh wrote:
> Hello,
>
> Why I can not do something like this in Postgres.
>
> SELECT 1 as a , 2 as b , a + b as c ;
>
> Regards
>
>
>
e for number
formatting
lc_time = 'en_GB.UTF-8' # locale for time formatting
default_text_search_config = 'pg_catalog.english'
Besides running VACUUM FULL pg_largeobject;, is there a way I can get
autovacuum to start and clear this up?
All the b
ink, but not just as a comparison against other RDBMS.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Thu, Dec 8, 2011 at 3:11 PM, Marc Cousin wrote:
> Le Thu, 8 Dec 2011 12:27:22 +,
> Simon Riggs a écrit :
>
>> On Thu, Dec 8, 2011 at 11:24 AM, Craig Ringer
>> wrote:
>>
>> > Areas in which Pg seems significantly less capable include:
>>
>>
assignment xtop 2268215780: subxacts: 2268215781 2268215782
Looks like the bug fixed in 9.1.2 and 9.0.6
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgres
machine. Some limited level is possible with external pooling, but only by
> limiting concurrent workers.
> - prioritisation of queries or users. It's hard to say "prefer this query
> over this one, give it more resources" or "user A's work always preempts
> user B&
would cause
the md5 checksum to change. So it cannot be the btree code at
_bt_delitems_vacuum() causing this.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgre
On Tue, Nov 22, 2011 at 7:32 AM, marcin kowalski wrote:
> i'm simply stopping postgresql
If you do do pg_ctl stop -m immediate then the copy will be corrupt.
You need to do a correct shutdown for it to work.
--
Simon Riggs http://www.2ndQuadrant.com/
Po
a wan) in
> order to be able to perform a PITR also at the replica site.
> Thanks a lot for your help,
Not directly, but you can arrange this yourself.
Cascading replication is a feature in PG 9.2, released next year.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL De
On Fri, Nov 18, 2011 at 3:18 PM, Tom Lane wrote:
> What Thom's complaining about is that the buffer may be marked dirty
> unnecessarily, ie when there has been no actual data change.
OK, I'll patch it.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL D
with nitems == 0 when it is
the last block of the relation with wal_level = hot standby
As discussed in the comments we must issue a WAL record for the last
block, whatever else has occurred.
So the correct number of WAL records is emitted and I see no bug there.
--
Simon Riggs htt
s acceptable and normal activity, or is
>> something awry here?
>
> Well, it's expected given the current coding in the btree vacuum logic.
> It's not clear to me why it was written like that, though.
I'll take a look.
--
Simon Riggs http://www.2nd
o cache the new db.
Allowing writes to continue while we copy is more complex.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
e sessions sleep to ensure a consistent database
after the copy.
Is (2) a problem for you? In what way?
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-gene
up those values. It seems
> to work, I can run long queries (for statistics / reports) on the
> slaves just fine.
That reasoning isn't sound because it doesn't work like that.
Recycling WAL files has nothing to do with query cancelation on hot
standby.
--
Simon Riggs
you from getting replication working, but it won't
block anyone else either.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes t
le INSERTs, nor do they run
UPDATEs or DELETEs, so the above actions would cover 99% of use cases.
Can anyone give backup to that opinion, or alternate viewpoints?
Thanks,
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
we may wait for some time to find a good
starting point. That could be anywhere from seconds to hours,
depending upon the exact load on the master, but shouldn't be any
longer than your longest running write transaction executing at that
time.
--
Simon Riggs http
d do this."
No, this is a technology problem.
Toast pointers are 20 bytes per column, so with 500 columns that is
1 bytes - which will not fit in one block.
If you wish to fit this in then you should use a 2 dimensional array,
which will then be just 1 column and your data will fit.
--
;m storing are bigint.
Arrays are toastable, so you are getting an error from another source.
create table array_example as
select array_fill(1010110101010101, ARRAY[10], ARRAY[1])::bigint[]
as arraycol;
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development,
ng running transactions
end, which is workload dependent but transient.
It's possible we will find another way of doing this in a future release.
Until then, I suggest starting base backup to create the standby when
not running both long transactions and transactions with many
subtransaction
regenerate the standby than to catchup.
Also, at some point you will run out of space in pg_xlog, which would
make the master crash. So probably best to have an archive_command
that starts deleting or compressing files before disk fills, but that
means your slave can then never catch
easy to do.
"Exclusion constraints" are not limited to a single datatype either,
so you should be able to find a solution.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
tly backup: shutdown pg on primary, do a file system copy (for
> backup later), start pg again on primary
> c) the next morning, trigger the secondary and run a re-index for
> testing (ERRORS as described in thread)
I see no reason to expect errors there.
Something about your setup is suspe
ou're using warm standby, but when you say run
pg_start_backup() AFTER each nightly backup I admit to being confused.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-genera
operator with 2 fields ?
There's nothing in constraint exclusion that depends upon specific datatypes.
Let us know if you find a problem with floats.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via p
1 - 100 of 550 matches
Mail list logo
