Hello,
On the same station, i have 2 postgresql server: one for my postgis db
(v9.1) and so another installed with opener^7 (9.2). Unfortunalty, i noticed
i'm obliged to stop service for my postgresql postgis (9.1) in order to use
openerp7 (postgres9.2). I 'm surprised about that. There is there a
On 28/05/2013 10:57, image wrote:
> Hello,
>
> On the same station, i have 2 postgresql server: one for my postgis db
> (v9.1) and so another installed with opener^7 (9.2). Unfortunalty, i noticed
> i'm obliged to stop service for my postgresql postgis (9.1) in order to use
> openerp7 (postgres9.2
On 28 May 2013 11:57, image wrote:
> Hello,
>
> On the same station, i have 2 postgresql server: one for my postgis db
> (v9.1) and so another installed with opener^7 (9.2). Unfortunalty, i
> noticed
> i'm obliged to stop service for my postgresql postgis (9.1) in order to use
> openerp7 (postgre
Hi,
I'm reading code of nodeSeqscan, and was confused with ExecSeqMarkPos and
ExecSeqRestrPos. They are only called by ExecMergeJoin. Could merge join use
a plain seqscan as outer/inner plan? If not, what are they used for?
Thanks.
Raymond O'Donnell wrote:
> On 28/05/2013 10:57, image wrote:
> > Hello,
> >
> > On the same station, i have 2 postgresql server: one for my postgis db
> > (v9.1) and so another installed with opener^7 (9.2). Unfortunalty, i noticed
> > i'm obliged to stop service for my postgresql postgis (9.1)
On Tue, May 28, 2013 at 12:25 AM, wrote:
> Thank you Wolfgang, just one question, what "bio" means? In the part that
> says "69 bio EUR..."
>
In this case, billions.
--
Michael
* Amit Langote (amitlangot...@gmail.com) wrote:
> How does one validate a backup? Is there any generally practiced way
> of doing that? Or what do you mean when you say "tested" backups?
You restore from it and then query the restored database for expected
contents, at least.
Thanks,
On Tue, May 28, 2013 at 2:41 AM, Jov wrote:
> you can use the psql \drds command:
Perfect! Just what I was looking for. Thanks Jov, and thanks to Joe Conway
as well for a different solution.
Moshe
--
Moshe Jacobson
Nead Werx, Inc. | Manager of Systems Engineering
2323 Cumberland Parkway, Su
* DT (kurt...@hotmail.com) wrote:
> I'm reading code of nodeSeqscan, and was confused with ExecSeqMarkPos and
> ExecSeqRestrPos. They are only called by ExecMergeJoin. Could merge join use
> a plain seqscan as outer/inner plan? If not, what are they used for?
ExecSeqMarkPos and ExecSeqRestPos ar
Hello,
Up to now, we're working with openERP v.5. The server has installed on our
ubuntu server station. I succeed in sauvegarding database (v8.3 of pgsql)
via pg_dump.
I would like now restore this database into my new OPENerp server station
(windows7). I succeed in doing it thanks to psql but
On 05/28/2013 07:34 AM, image wrote:
Hello,
Up to now, we're working with openERP v.5. The server has installed on our
ubuntu server station. I succeed in sauvegarding database (v8.3 of pgsql)
via pg_dump.
I would like now restore this database into my new OPENerp server station
(windows7). I s
Hello,
On the same station, i have 2 postgresql server: one for my postgis db
(v9.1) and so another installed with opener^7 (9.2). Unfortunalty, i noticed
i'm obliged to stop service for my postgresql postgis (9.1) in order to use
openerp7 (postgres9.2). I 'm surprised about that. There is there a
On 5/28/2013 3:02 AM, Raymond O'Donnell wrote:
On 28/05/2013 10:57, image wrote:
>Hello,
>
>On the same station, i have 2 postgresql server: one for my postgis db
>(v9.1) and so another installed with opener^7 (9.2). Unfortunalty, i noticed
>i'm obliged to stop service for my postgresql postgis
On May 28, 2013, at 2:54 AM, image wrote:
> Hello,
>
> On the same station, i have 2 postgresql server: one for my postgis db
> (v9.1) and so another installed with opener^7 (9.2). Unfortunalty, i noticed
> i'm obliged to stop service for my postgresql postgis (9.1) in order to use
> openerp7 (po
Dear PostgreSQL gurus,
It seems that the comparison operator "=" is functioning as the assignment
operator ":=" in this plpgsql trigger script I wrote. I was under the
impression that "=" is only for comparison and not assignment. If this is
true, please explain the transcript below. If it's not t
* Moshe Jacobson (mo...@neadwerx.com) wrote:
> It seems that the comparison operator "=" is functioning as the assignment
> operator ":=" in this plpgsql trigger script I wrote. I was under the
> impression that "=" is only for comparison and not assignment. If this is
> true, please explain the tr
2013/5/28 Stephen Frost :
> * Moshe Jacobson (mo...@neadwerx.com) wrote:
>> It seems that the comparison operator "=" is functioning as the assignment
>> operator ":=" in this plpgsql trigger script I wrote. I was under the
>> impression that "=" is only for comparison and not assignment. If this i
On Tue, May 28, 2013 at 4:06 PM, Stephen Frost wrote:
> Both are supported. It's not really documented as using '=' is
> considered 'legacy' but it's also extensively used and removing it would
> break quite a bit of code for people.
>
This is crazy! By leaving it in, they are allowing my obsol
* Moshe Jacobson (mo...@neadwerx.com) wrote:
> Any PG committers who can change this in 9.3?
It will certainly not be changed for 9.3.
As suggested, perhaps in 10.0, but I tend to doubt it. It will
certainly be mentioned in the release notes when it happens.
Thanks,
Ste
On 05/28/2013 01:06 PM, Stephen Frost wrote:
* Moshe Jacobson (mo...@neadwerx.com) wrote:
It seems that the comparison operator "=" is functioning as the assignment
operator ":=" in this plpgsql trigger script I wrote. I was under the
impression that "=" is only for comparison and not assignment
Hello
2013/5/28 Moshe Jacobson :
> On Tue, May 28, 2013 at 4:06 PM, Stephen Frost wrote:
>>
>> Both are supported. It's not really documented as using '=' is
>> considered 'legacy' but it's also extensively used and removing it would
>> break quite a bit of code for people.
>
>
> This is crazy!
2013/5/28 Steve Crawford :
> On 05/28/2013 01:06 PM, Stephen Frost wrote:
>>
>> * Moshe Jacobson (mo...@neadwerx.com) wrote:
>>>
>>> It seems that the comparison operator "=" is functioning as the
>>> assignment
>>> operator ":=" in this plpgsql trigger script I wrote. I was under the
>>> impressio
I'm having some issue with BLOB updates (via ECPG). The total blobs size
should be ~280MB, but after partially updating all of them for 150 times
the size on disk grows up from 184MB to 18GB.
In more details:
There are 608 blobs of size 460800 bytes. All blobs are updated
piecewise in 150 rep
23 matches
Mail list logo
