>
> On googling, it seems this is related to .Net framework compatibility. I am
> using .Net Framework 4 to build the program.cs and that is what I have
> on my m/c. Are you using the same for Npgsql or some different version?
>
That is probably the problem. Npgsql 3.0 is only available for .NET
On Mon, Sep 28, 2015 at 07:17:39AM +0300, Amir Rohan wrote:
> The docs seem to be in need of some improvement, primarily because
> it has the feel of having been monkey-patched repeatedly it in the
> past. It needs to have someone with more experience read through it
> and comment on technical accu
On Sat, Oct 31, 2015 at 10:14:18AM +0100, Simon Riggs wrote:
> I agree with Filip that this is a bug. pg_dump clearly doesn't work
> correctly with inheritance.
>
> If I run this command
>
> pg_dump -t tab1
>
> then I get a dump of "tab1". No data is included from tables that inherit
> tab1 b
On Thu, Dec 31, 2015 at 7:42 PM, Jesper Pedersen wrote:
> On 12/31/2015 06:36 AM, Amit Kapila wrote:
>
>> Going further on this work, I have written a patch for separating the
>> tranches for extensions. The basic idea is to expose two new API's,
>> first to request a new tranche and second to a
On Tue, Sep 01, 2015 at 12:33:26AM -0500, Jim Nasby wrote:
> On 8/29/15 5:52 PM, Jeff Janes wrote:
> >If 2 other backends have a pin, only the last one to drop it should do
> >the waking. I don't see a way they could both try to do the waking, the
> >interlock on the buffer header seems to prevent
On Thu, Sep 03, 2015 at 11:04:11PM -0400, Tom Lane wrote:
> *** AtSubAbort_Portals(SubTransactionId mySu
> --- 909,966
> {
> Portal portal = hentry->portal;
>
> + /* Was it created in this subtransaction? */
> if (portal->c
Failover Slots
If Logical Decoding is taking place from a master, then if we failover and
create a new master we would like to continue the Logical Decoding from the
new master. To facilitate this, we introduce the concept of “Failover
Slots”, which are slots that generate WAL, so that any downstr
I wrote:
> Now, one line of thought here is that flatten_reloptions() is out of its
> mind to not be worrying about quoting the reloption values. And perhaps
> it is, but I think if we go that direction, we may be fighting similar
> fires for awhile to come. psql's describe.c, for example, doesn'
> On Jan 1, 2016, at 11:14 AM, Tom Lane wrote:
>
> Oleg Bartunov writes:
>> I noticed, that psql's \e command doesn't worked for me complaining 'error
>> opening file'. I did research and found that following setting in joe's (if
>> I choose editor as joe) configuraton causes the problem:
>> -e
Oleg Bartunov writes:
> I noticed, that psql's \e command doesn't worked for me complaining 'error
> opening file'. I did research and found that following setting in joe's (if
> I choose editor as joe) configuraton causes the problem:
> -exask ^KX always confirms file name
> That worked f
On Fri, Jan 1, 2016 at 4:40 PM, Amit Kapila wrote:
> On Wed, Dec 30, 2015 at 10:31 PM, Shay Rojansky wrote:
>
>> OK, I finally found some time to dive into this.
>>
>> The backends seem to hang when the client closes a socket without first
>> sending a Terminate message - some of the tests make
On Thu, Dec 31, 2015 at 9:13 AM, Michael Paquier
wrote:
> On Wed, Dec 30, 2015 at 11:21 PM, Alvaro Herrera
> wrote:
>> Michael Paquier wrote:
>>
>>> OK, here are new patches.
>>> - 0001 switches a bunch of TailMatches to Matches. Do we want to care
>>> about the case where a schema is created fol
Recently,
I noticed, that psql's \e command doesn't worked for me complaining 'error
opening file'. I did research and found that following setting in joe's (if
I choose editor as joe) configuraton causes the problem:
-exask ^KX always confirms file name
That worked for decades :), so I'
On Wed, Dec 30, 2015 at 10:31 PM, Shay Rojansky wrote:
> OK, I finally found some time to dive into this.
>
> The backends seem to hang when the client closes a socket without first
> sending a Terminate message - some of the tests make this happen. I've
> confirmed this happens with 9.5rc1 runni
14 matches
Mail list logo
