On Tue, Mar 20, 2012 at 2:59 AM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 6545
> Logged by: AYACHI ABDELAKDER
> Email address: ka...@hotmail.fr
> PostgreSQL version: 8.3.15
> Operating system: poker traker 3
> Description:
>
> apres avoir
On Mon, Mar 26, 2012 at 1:41 AM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 6557
> Logged by: vikas a
> Email address: vikas.ar...@rbs.com
> PostgreSQL version: 9.0.1
> Operating system: Linux and Windows
> Description:
>
> Hi
>
> I am using
On Thu, Mar 15, 2012 at 3:04 PM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 6534
> Logged by: Barry Bell
> Email address: barry_b...@harte-hanks.com
> PostgreSQL version: 9.1.2
> Operating system: Windows Server 2003
> Description:
>
> Using
On Mon, Mar 19, 2012 at 1:16 PM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 6542
> Logged by: DELCROIX Frédéric
> Email address: f.delcr...@rdvnet.fr
> PostgreSQL version: 9.0.7
> Operating system: windows Xp/vista/seven
> Description:
>
> W
On Tue, Mar 13, 2012 at 1:12 PM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 6530
> Logged by: Kasper Sandberg
> Email address: kont...@sandberg-consult.dk
> PostgreSQL version: 9.1.3
> Operating system: Debian squeeze
> Description:
>
> Hell
On Tue, Mar 13, 2012 at 5:00 AM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 6528
> Logged by: Stuart Bishop
> Email address: stuart.bis...@canonical.com
> PostgreSQL version: 9.1.3
> Operating system: Ubuntu
> Description:
>
> In section 24.
On Tue, Mar 6, 2012 at 12:46 AM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 6521
> Logged by: Jeongho Jeon
> Email address: maczn...@gmail.com
> PostgreSQL version: 9.1.1
> Operating system: Windows 7
> Description:
>
> Hi!
>
> PostgreSQL 9.
On Tue, Mar 6, 2012 at 10:15 AM, Matteo Sgalaberni wrote:
> Hi people!
>
> I have a pg 8.3. Today I issued in a database that comand:
> =# ALTER TABLE cliente ADD COLUMN pwd_expired boolean DEFAULT FALSE;
> WARNING: unexpected attrdef record found for attr 22 of rel cliente
> WARNING: unexpected
On Sat, Feb 18, 2012 at 5:37 AM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 6464
> Logged by: Lucian Naie
> Email address: lucian.n...@gmail.com
> PostgreSQL version: 9.1.2
> Operating system: Windows 7 Ultimate SP1, x86, 64 bit machine
> De
On Wed, Feb 22, 2012 at 7:28 AM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 6481
> Logged by: Michał Rakoczy
> Email address: michal.rako...@sb-betting.com
> PostgreSQL version: 9.0.5
> Operating system: Windows Server 2008 R2 Enterprise x64
On Thu, Mar 29, 2012 at 3:36 AM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 6565
> Logged by: Guillaume Cottenceau
> Email address: gcott...@gmail.com
> PostgreSQL version: 9.1.3
> Operating system: not relevant
> Description:
>
> 9.0 releas
On Mon, Apr 9, 2012 at 9:56 AM, Robert Haas wrote:
> On Tue, Mar 20, 2012 at 2:59 AM, wrote:
>> The following bug has been logged on the website:
>>
>> Bug reference: 6545
>> Logged by: AYACHI ABDELAKDER
>> Email address: ka...@hotmail.fr
>> PostgreSQL version: 8.3.15
>> Opera
Robert Haas writes:
> We do have this:
>
>The operators &&, @> and
><@ are equivalent to PostgreSQL's built-in
>operators of the same names, except that they work only on integer arrays
>that do not contain nulls, while the built-in operators work for any array
>type. This
On Mon, Apr 09, 2012 at 10:10:34AM -0400, Robert Haas wrote:
> On Tue, Mar 13, 2012 at 5:00 AM, wrote:
> > The following bug has been logged on the website:
> >
> > Bug reference: 6528
> > Logged by: Stuart Bishop
> > Email address: stuart.bis...@canonical.com
> > PostgreSQL ve
Bruce Momjian wrote:
> Robert Haas wrote:
>> wrote:
>>> In section 24.3.5.1 of the docs on setting up continuous
>>> archiving, there are a few paragraphs and examples for using
>>> pglesslog (pg_compresslog and pg_decompresslog). This tool did
>>> not get out of beta for 9.0 and the only repor
Excerpts from Bruce Momjian's message of lun abr 09 15:13:10 -0300 2012:
> On Mon, Apr 09, 2012 at 10:10:34AM -0400, Robert Haas wrote:
> > This complaint appears to be accurate. I think we should go ahead and
> > remove that mention.
>
> Agreed; removed with the attached patch. I didn't both
On Mon, Apr 09, 2012 at 03:37:09PM -0300, Alvaro Herrera wrote:
>
> Excerpts from Bruce Momjian's message of lun abr 09 15:13:10 -0300 2012:
> > On Mon, Apr 09, 2012 at 10:10:34AM -0400, Robert Haas wrote:
>
> > > This complaint appears to be accurate. I think we should go ahead and
> > > remov
Bruce Momjian wrote:
> On Mon, Apr 09, 2012 at 03:37:09PM -0300, Alvaro Herrera wrote:
>> (Another related tool is clearxlogtail which zeroes areas from
>> WAL files when they are empty because of an early switch due to
>> archive timeout).
>
> Should we document that?
Our shop has been using
yes, I could not figure out why my GIN index was not used, this is what
i meant.
On 09/04/12 18:16, Tom Lane wrote:
Robert Haas writes:
We do have this:
The operators&&,@> and
<@ are equivalent toPostgreSQL's built-in
operators of the same names, except that they work only o
In ODBC while binding variable using SQLBindParameter(..) API you might be
using SQL_DOUBLE or SQL_Numeric or some similar datatype to send the
variable, thats why in postgres it is showing as "Double precision"
-Original Message-
From: pgsql-bugs-ow...@postgresql.org
[mailto:pgsql-bugs-o
Robert Haas writes:
> On Thu, Mar 29, 2012 at 3:36 AM, wrote:
>> """GEQO's searching is randomized and therefore its plans may vary
>> nondeterministically."""
>>
>> I guess this sentence is outdated now?
> Hmm, sounds like it. Does anyone think otherwise?
Well, you could still argue that it
21 matches
Mail list logo
