On 7/30/15 3:09 PM, Alban Hertroys wrote:
COPY is a bit special, I'm afraid. For starters, although it works_like_ doing
a bunch of INSERTs, it doesn't perform actual INSERTs. Apparently, that also
means it won't fire an INSERT rule and thus can't be used with an updatable
view. There are no
On 8/4/15 2:47 AM, Jan Keirse wrote:
CAST (age(relfrozenxid) AS real) / CAST(trunc(((2^32)/2)-1-100) AS real)
>AS perc_until_wraparound_server_freeze
>
>
>(Note that we do this at the table level rather than the database level like
>you did, though, so that we have the information we need to
On 08/04/2015 08:12 AM, Killian Driscoll wrote:
On 4 August 2015 at 17:02, Adrian Klaver mailto:adrian.kla...@aklaver.com>> wrote:
On 08/04/2015 07:48 AM, Killian Driscoll wrote:
CCing list
FYI, I will be away from my computer. Someone else will have to
follow up to my questio
On 08/04/2015 12:47 PM, clingare...@vsoftcorp.com wrote:
Hi,
Please help me on:
what is the use of bidirectional replication in PostgreSQL?
How BDR works?
how to setup BDR?
on which versions BDR works?
Please do not cross post. What you are looking for is here:
http://bdr-project.org/do
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Tobias Fielitz
Sent: Monday, August 03, 2015 9:56 PM
To: pgsql-general@postgresql.org
Subject: [GENERAL] Get additional constraint information
select * from information_schema.table_constraints whe
I would suggest going to http://bdr-project.org/docs/stable/index.html
On Tue, Aug 4, 2015 at 3:47 PM, wrote:
> Hi,
>
>
>
> Please help me on:
>
>
>
> what is the use of bidirectional replication in PostgreSQL?
>
> How BDR works?
>
> how to setup BDR?
>
> on which versions BDR works?
>
>
>
> Th
Hi,
Please help me on:
what is the use of bidirectional replication in PostgreSQL?
How BDR works?
how to setup BDR?
on which versions BDR works?
Thanks & regards,
Chandra kiran
Please do not print this email unless it is absolutely necessary.
This email and any files transmitted with
select * from information_schema.table_constraints where
table_name=‘install_crash’;
Results here: http://imgur.com/YymSvBS
How can I get more information about these constraints, especially on which
columns the not null constraints are?
Thanks
Tobias FielitzCTO StreetHawk
+61404267511
tob
On 4 August 2015 at 17:02, Adrian Klaver wrote:
> On 08/04/2015 07:48 AM, Killian Driscoll wrote:
>
> CCing list
>
> FYI, I will be away from my computer. Someone else will have to follow up
> to my questions below.
>
>>
>>
> So that is not the server you set up, correct?
>>
>>
>> I am using
On 08/04/2015 07:48 AM, Killian Driscoll wrote:
CCing list
FYI, I will be away from my computer. Someone else will have to follow
up to my questions below.
So that is not the server you set up, correct?
I am using the postgresql on localhost 5432. The OpenGeo\pgsql is
something I set
On 08/04/2015 06:48 AM, Killian Driscoll wrote:
Please do not top post, thanks. - no idea what that means.
See here:
https://en.wikipedia.org/wiki/Posting_style#Top-posting
vs
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
or
https://en.wikipedia.org/wiki/Posting_style#B
On 8/4/2015 6:14 AM, Melvin Davidson wrote:
As additional advice, to get the best performance, you will want all
your tablespaces to be on separate spindles/disks.
EG: disk1/tblspc1
disk2/tblspc2
disk3/tblspc3
...
disk99/tblspc99
actually, I find to get best pe
On 08/04/2015 06:25 AM, Killian Driscoll wrote:
CCing list
Please do not top post, thanks.
All the databases are one one server on localhost 5432
And you have verified this my looking at the Windows process monitor?
The reason I keep asking is that is looks very much like you are
connectin
On 08/04/2015 01:58 AM, Killian Driscoll wrote:
I am using postgresql 9.3 with pgadmin III, and Access 2013 as a front
end for data entry using (ODBC connection) linked tables, on a Windows
8.1 (64).
I have one main database I am developing on a localhost:5432, with four
other test databases I h
As additional advice, to get the best performance, you will want all your
tablespaces to be on separate spindles/disks.
EG: disk1/tblspc1
disk2/tblspc2
disk3/tblspc3
...
disk99/tblspc99
On Tue, Aug 4, 2015 at 5:31 AM, Albe Laurenz
wrote:
> Chris Withers wrote:
> >
Chris Withers wrote:
> This raises an interesting question: can a child table be in a different
> tablespace to its parent and other children of that parent?
Yes.
Inheritance is a logical concept and is independent of physical placement.
Yours,
Laurenz Albe
--
Sent via pgsql-general mailing li
On Tue, Aug 4, 2015 at 2:28 PM, Killian Driscoll
wrote:
> I am using postgresql 9.3 with pgadmin III, and Access 2013 as a front end
> for data entry using (ODBC connection) linked tables, on a Windows 8.1 (64).
>
> OK.
> I have one main database I am developing on a localhost:5432, with four
>
I am using postgresql 9.3 with pgadmin III, and Access 2013 as a front end
for data entry using (ODBC connection) linked tables, on a Windows 8.1 (64).
I have one main database I am developing on a localhost:5432, with four
other test databases I had on the same localhost. A few weeks ago the four
On 04/08/2015 09:11, Seref Arikan wrote:
I work in healthcare and patient centric records let me consider
multiple servers for lots and lots of patients. The
engineering team
from instagram has been sharing their experience with
postgres, which is
possib
On Tue, Aug 4, 2015 at 9:06 AM, Chris Withers
wrote:
> On 03/08/2015 08:34, Seref Arikan wrote:
>
>>
>>
>> At what point does postgres stop scaling?
>> What happens when the computational load no longer fits on one
>> machine? What are the options then?
>>
>>
>> I think it is hard to
On 03/08/2015 08:34, Seref Arikan wrote:
At what point does postgres stop scaling?
What happens when the computational load no longer fits on one
machine? What are the options then?
I think it is hard to come up with blanket responses to generic
questions such as "What happens wh
On 03/08/2015 08:40, Jony Cohen wrote:
Servers now days reach very impressive write speeds and at rather low
prices - it's simpler to split the write to 2 tables on different
tablespaces/devices than 2 servers.
This raises an interesting question: can a child table be in a different
tablespace t
On Tue, Aug 4, 2015 at 6:24 AM, William Dunn wrote:
> Hello Jan,
>
> I think your calculation is slightly off because per the docs when
> PostgreSQL comes within 1 million of the age at which an actual wraparound
> occurs it will go into the safety shutdown mode. Thus the calculation should
> be (
23 matches
Mail list logo