se, then it probably is because of
the uppercase letters. Try this way:
REINDEX DATABASE "PremierIEX"
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
Phone: +593 4 5107566 Cell: +593 987171157
--
Sent via pgsql-bugs mailing
row)
select postgis_geos_version();
postgis_geos_version
--
3.3.8-CAPI-1.7.8
(1 row)
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
Phone: +593 4 5107566 Cell: +593 987171157
--
Sent via pgsql-bugs mailing list
LECT idusuario, clave,
> nombreusuario, rol, idpersona FROM Farmacia.public.usuario WHERE
> ((nombreusuario = ?) AND (clave = ?))")
>
>
This is not actually a bug but a well known postgresql limitation, you
can't use database references in the from.
I answered to the OP, explaining that and
ay, seems that you need an additional index on SARS_ACTS_RUN.ALGORITHM
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
Phone: +593 4 5107566 Cell: +593 987171157
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To ma
l-es-ay...@postgresql.org so we can a)
speak spanish and b) determine what your problem is.
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
Phone: +593 4 5107566 Cell: +593 987171157
--
Sent via pgsql-bugs mailing list (pgsql-
cters."
if you only want to show those that contains an underscore (supressing
its wildcard behaviour) you need to use a escape character:
col LIKE '%\_%'
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
Phone: +593 4 5107566
about your question, i guess the compromise Álvaro was taken here is
to affect all objects that could be *seen* from this database you
can't climb to other objects in other databases because they can't be
seen.
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: So
the
>> design intention. I doubt that we want DROP OWNED dropping whole
>> databases. At most maybe we should raise a NOTICE?
>
> I broke it recently: fe3b5eb08
>
whatever is the right way to solve this... shouldn't we do something
similar in shdepReassignOwned() in
l
> Would upgrading from 4.1.6.Final to Hibernate 4.1.7 in Linux, fix this
> partitioning ingest problem?
>
don't know, but that certainly looks like a hibernate bug, not a postgresql one
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
ess, it has the hstore data type in it from before the extension
> system exists. You need to follow the upgrade instructions to convert it to
> an extension.
what about adding a HINT there? something like "you probably need to
use CREATE EXTENSION ... FROM unpackaged"
--
Jaime C
a
>
FYI, this seems like a pilot error not a bug so i moved it to the
spanish list and asked some additional info to OP
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
ests on windows 7
home premium...
http://pgbuildfarm.org/cgi-bin/show_status.pl?member=chough&member=pitta
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make
n
pgbr-ge...@listas.postgresql.org.br
Anyway, can you explain what grant did you execute? what permissions
the user had previously?
for example, did you grant use of the schema and the table?
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
--
aa53348cc16a5473a
>
> I take it you're using something older than 9.1.
>
that's a quick reaction :D
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make chang
On Thu, Apr 26, 2012 at 5:35 PM, Josh Berkus wrote:
>
> Also, have we discussed maybe hiding these schemas from \dn?
>
+1 from this idea... maybe do them visible only on \dn+
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
--
Sent
o make this query behave
normally again.
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Sun, Mar 18, 2012 at 8:11 AM, Dave Page wrote:
>
>
> On Sunday, March 18, 2012, Jaime Casanova wrote:
>> On Sun, Mar 18, 2012 at 12:13 AM, prem tolani
>> wrote:
>>> Below error occurs only when i restart postgre 8.1 service when
>>> applicaion is runn
below email.
>
postgres 8.1 is not currently supported (since November 2010,
http://www.postgresql.org/support/versioning), so is likely that if
something was done in postgres to support win7 it hasn't reach 8.1
the best "fix" you can get is to migrate to a newer supported version
a
our problem using EXECUTE:
CREATE FUNCTION countusers()
RETURNS INT
AS $PROC$
DECLARE
counter INT;
BEGIN
EXECUTE 'SELECT count(*) FROM users' INTO counter;
RETURN counter;
END
$PROC$ LANGUAGE 'plpgsql' VOLATILE;
--
Jaime Casanova www.2ndQuadrant.com
Professional P
on:
>
> Note if I change logon to Local System Account from this account it will
> start but the database's do not work.
>
maybe the eventlog shows some error? please look and send if there is any
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x
2012/1/11 :
> The following bug has been logged on the website:
>
This is not a bug.
and just for the record i redirected the mail with an explanation (and
a brief answer to his problem) to pgsql-es-ayuda where OP can found
more help in spanish
--
Jaime Casanova www.2ndQuadra
http://www.postgresql.org/docs/9.1/static/hot-standby.html#HOT-STANDBY-USERS
> Is there any workaround?
> How could we create temp database and tables on slave?
>
not with streaming replication
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitaci
oncurrent also,
but at least faster... unless i'm missing something
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
bility issues
> with PostgreSQL.
> Could you please connect me to the appropriate
> individual for this?
>
if you think this compatibility issue is a bug of postgresql, this
list is just fine otherwise write to pgsql-hack...@postgresql.org...
--
Jaime Casanova www.2ndQuadrant.com
gt; and no_active"
> PL/pgSQL function "enablenode_int" line 32 at SQL statement
>
what do you have in timezone in postgresql.conf? certainly, the
timestamp format looks odd
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL
Craig Ringer writes:
> -ENOCOFFEE
>
LOL. this one is the best i have heard this year
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL
Soporte 24x7, desarrollo, capacitación y servicios
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make chan
');
>
> By the way, another issue that I found is when I execute \df. It
> doesn't display anything (I must
> force with * to do that).
i can confirm this
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
--
Sent via pgsql-bugs
to the standby (because the standby
is a synchronous standby, it keeps waiting until the standby aknlowdge
to have received the wal), so what you are cancelling now is the
primary waiting for the standby...
btw, i guess we should be defaulting to asynchronous standbys (ie:
synchronous_commit=loc
estion from the page Hubert show you
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
information to
determine what the problem is, which you obviously haven't do it.
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
postgresql.org? besides, a report needs a lot more info,
for example postgresql version, operating system, exact message
errors, and so on
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
--
Sent via pgsql-bugs mailing list (pgsql-bugs@post
: Installation error
> Details:
>
> When trying to install version 9.0.2 in a Win XP 32 get the error :
>
> "Unable to write inside TEMP environment variable path"
>
this seems a permissions issue, are you using an Administrator account
or something with enough
the trigger inserting a new value on the
same table forcing a new execution of the trigger making it
recursive...
> I am thinking its a bug in postgres..
it's too early to blame postgres
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de Postgre
him some code to try... anyone remeber
some change in that area or in an area that could affect the npgsql
driver?
--
Jaime Casanova www.2ndQuadrant.com
Soporte y capacitación de PostgreSQL
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
how do you determine it is corrupted?
3) it gives you some error messages? which one?
4) How old is the data that you loss?
5) are you aware that you have to have write-cache disabled on your
disks in other to assure the data get it to the disk?
6) how frequent are you executing VACUUM?
--
Jaime C
27;;
then add to pg_hba.conf a line like this:
host dbname username ip_web_server/32 md5
--
Jaime Casanova www.2ndQuadrant.com
Soporte y capacitación de PostgreSQL
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your sub
-- Forwarded message --
From: 陳裕耀
Date: 2010/4/22
Subject: Re: [BUGS] BUG #5433: pg_dump (8.4.3) copy database failure!
To: Jaime Casanova
於 2010/4/22 下午 12:56, Jaime Casanova 提到:
On Wed, Apr 21, 2010 at 11:21 PM, y.y.Chen wrote:
pg_dump in A=> pg_dump -h A db >
A to A for that
database and user?
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ike
patch reviewers but they just respond the easy ones, and let difficult
ones for more experienced people, and maybe something like "fix bug
fest" maybe at the end of commit fests?
of course most of this is just a dream, or not?
--
Atentamente,
Jaime Casanova
Soporte y capacita
a @$#! bug tracker.
>
after seen the commitfest app, i can swear the bug tracker you write
should be cool
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
--
Sent via pgsql-bugs mailing list (p
ct list :(
besides my abilities with web forms are very poor... but if some one
is willing to help me a little i can try
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
--
Sent via pgsql-bugs mailin
bug report form should only be used for reporting bugs and
problems with the PostgreSQL database. Problems with database
connectors such as ODBC and JDBC, graphical administration tools such
as pgAdmin or other external projects should not be reported here;
please report to those projects directly.
. then we can announce 10.0
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
e sistem,
> the paga that do it dont work.
>
how do you install it? what do you mean by: "i can open a database but
in the sistem, the paga that do it dont work.". you have any install
errors?
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo
was created with uppercase you could need to
quote "ColumnName" (this is not single quote, though)
can you give a simple test case? i mean, a create table (maybe some
test data) and a select... that works the way you describe on those
OSes
--
Atentamente,
Jaime Casanova
Soporte y capa
On Thu, Jan 21, 2010 at 12:45 PM, Tom Lane wrote:
> Jaime Casanova writes:
>> When we perform a test migration of the data we found some errors on
>> the logs, one of them is this one:
>
>> """
>> mic=# ALTER TABLE tcom_invitacion ADD primary key (
get this
same error (not always, it seems this time the index is being created
but this time i did it inside a transaction)...
doesn't the index creation of the index block the table so, that
message should not appear?
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreS
ad of simply 'duration >= '
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Thu, Nov 19, 2009 at 1:03 PM, Orange wrote:
>
> Hi it shows like you see bellow
>
> The stange that once I copy it to other file it shows right
>
and this is related to postgres... because...
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría
On Sun, Sep 27, 2009 at 9:45 PM, Robert Haas wrote:
>
> (with apologies to anyone on this mailing list who ACTUALLY speaks
> Spanish - it must have hurt to read that)
>
actually it was very good!
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y d
0'::timestamp with time zone;
timestamptz
---
1900-01-01 00:00:00-05:14
(1 row)
"""
is this intended? why we treat '1900-01-01 00:00:00' different?
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y
uot;test_foo" line 5 at RETURN QUERY
>
yeah! that bug was fixed here
http://archives.postgresql.org/pgsql-committers/2009-08/msg00068.php
but only in the currently in develop 8.5
are we going to backpatch this? while i think we should i know nothing
about how feasible that is
--
Atenta
+
bpprovee | 111 | 0
(1 row)
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
MySQL migration wizard does not start
> Details:
>
> I have downloaded and installed PostgreSQL 8.4 and installed the mysql
> migration wizard.
MySQL migration wizard is a tool from EnterpriseDB
(http://www.enterprisedb.com), you should go ask them...
--
Atentamente,
Jaime Casano
ter position in both strings where the
> letters become different.
>
this is completely non-sense. can you present a test case that proves
what you're claiming?
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel.
On Fri, Aug 21, 2009 at 2:58 PM, Robert Haas wrote:
>
> Maybe you are doing this inside a transaction someplace? If so, it
> won't be visible to other transactions until you commit.
>
but then, if he simply restart the service the transaction will rollback
--
Atentament
. you have a specific problem of this kind?
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ers/2009-07/msg00210.php
>
> It will be in 8.4.1.
>
> regards, tom lane
>
if you can compile code then you can download the latest snapshot of
8.4.0 (with the fix) from here
http://www.postgresql.org/ftp/snapshot/stable/8.4/
--
Atentamente,
Jaime Casanova
S
On Tue, Jul 28, 2009 at 12:12 PM, Robert Haas wrote:
>>>
>>> patch attached
>>>
>> super, thanks
>>
>> Pavel
>
> So is this Ready for Committer?
>
i think so... but being me who added the last bit of code i didn't
felt confident to ma
ou know if this bug has been fixed or not? What would be the solution
> then?
>
That was fixed in 8.3.6
(http://www.postgresql.org/docs/8.4/static/release-8-3-6.html) but we
are in 8.3.7 now better go to the last...
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Ase
On Mon, Jul 20, 2009 at 11:34 AM, Jaime
Casanova wrote:
> On Mon, Jul 20, 2009 at 10:09 AM, Alvaro
>>
>> Getting rid of the check on natts was "ungood" ... it needs to compare
>> the number of undropped columns of both tupdescs.
>>
>
> ah! ok, i see...
On Mon, Jul 20, 2009 at 10:09 AM, Alvaro
Herrera wrote:
> Tom Lane escribió:
>> Jaime Casanova writes:
>> > this one applies, compiles and it actually fixes the bug...
>>
>> And introduces a bunch of new ones. Surely you don't think that version
>&g
On Mon, Jul 20, 2009 at 9:55 AM, Tom Lane wrote:
> Jaime Casanova writes:
>> this one applies, compiles and it actually fixes the bug...
>
> And introduces a bunch of new ones. Surely you don't think that version
> of compatible_tupdesc() is good enough.
>
i gue
thing like that) for avoiding
duplicate code... but that's another patch, is worth the trouble?
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
Index: src/pl/p
cc: the -list this time
-- Forwarded message --
From: Jaime Casanova
Date: Thu, Jul 16, 2009 at 5:18 PM
Subject: Re: [BUGS] WARNING: out of shared memory
To: "Juan C. Aragon"
it's better for you to always write to the list because there are more
people that c
bug
happen)?
>
> Also, we are not able to login to the database with PgAdmin, getting same
> error “out of shared memory”
>
what's the value in max_connections?
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ec
a problem that looks a lot like the
one you reported here...
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your sub
ld have been specified that way...
i say pay the price for WITH HOLD and SCROLL and don't allow scrolling
ability if SCROLL hasn't been specified
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +5938717115
On Tue, May 12, 2009 at 11:57 AM, Rodrigo Peres Chapelin
wrote:
> Hi,
>
> can i install Postgresql 8.2.3 on Red Hat 5 64 bits?
>
is this a bug of some kind?
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil -
t into t values (0,'30 days'), (1,'1 month');
>> INSERT 0 2
>> test-std=# select * from t as a, t as b where a.i=b.i;
>
> Reproducible in 8.2.13 as well ..
>
and the same in HEAD
PS: the analyze not always brings the problems, i had to turn off
enable_merge
D CHECK (length(column) =
a_value) as many times as you want without the need for a table
rewrite
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.
BLE ... TYPE.
now, back to the problem... is not easier to define a column as TEXT
and to put a check to constraint the length? if you wanna change the
constraint that will be almost free
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaq
the error message? a little test case would be useful
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscripti
On Mon, Mar 2, 2009 at 12:21 PM, Tom Lane wrote:
>
> Before considering complicating the definition of lastval, I'd vote
> for removing it entirely. It's a foot-gun and will never be anything
> but.
>
+1
--
Atentamente,
Jaime Casanova
Soporte y capacitación
nd this??
>
ah? from where do you download it? are you sure it's not asking you to
*assign* a password for the postgres database user?
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
--
Sent via p
o confusions about the order
of columns in INSERT statements, eventually you will be forced to put
column names in every INSERT statement (ie: if you start to work in an
enterprise with an already implemented postgres database)
--
Atentamente,
Jaime Casanova
Soporte y capacitación de Postg
tp://archives.postgresql.org/pgsql-bugs/2008-06/msg00175.php
if you can compile postgres from sources you can apply the fix Tom
shows. If not you have to wait for 8.3.4.
Is not time for a new minor release?
--
regards,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de s
; Example - field employeeName in table Employees
postgres converts all your uppercase in object names to lowercase...
if you really want mixed case you must put the name in quotes.
Try with:
ALTER TABLE "Employees" ADD CONSTRAINT employeenametest
CHECK (employeename != 'Ke
le nobody else has either. It's a PostgreSQL
> > extension, so people arriving from outside don't even know it exists,
>
> Say again? Both the SCROLL option to DECLARE CURSOR and FETCH PRIOR are
> straight out of the SQL92 spec.
>
i think Simon is talking about DISTI
On Sat, May 17, 2008 at 1:45 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> [ redirecting to -bugs ]
>
> "Jaime Casanova" <[EMAIL PROTECTED]> writes:
>> On Sat, May 17, 2008 at 11:55 AM, Tom Lane <[EMAIL PROTECTED]> wrote:
>>> "Jaime Casanova&
t to the reader to interpret the two separate
representations as meaning a single time point based on the context.
"""
--
regards,
Jaime Casanova
Soporte de PostgreSQL
Guayaquil - Ecuador
Cel. 087171157
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
t and specifically for bugs reporting. If you
want help with your work and because of the nature of it yo can write
in english to [EMAIL PROTECTED] or to
[EMAIL PROTECTED] if you don't know english you can write
in spanish to [EMAIL PROTECTED]
--
regards,
Jaime Casanova
"Programming today
-- Forwarded message --
From: Fadi Thabtah <[EMAIL PROTECTED]>
Date: Sun, 1 Jul 2007 12:56:52 +0100
Subject: RE: [BUGS] BUG #3421: Failed to create temporary batch file
To: Jaime Casanova <[EMAIL PROTECTED]>
yes I do.
Fadi
From: Ja
batch file
Details:
I was unable to install Postgres because of the following message "Failed to
create temporary batch file", which interrupts the installation.
do you have write permissions on the directory you are installing at?
--
regards,
Jaime Casanova
"Programming to
e +/-10 records affected. each mov_id can hold one or more (usuals up to
5) names. but here, the subquery seemed to return ~3700 distinct mov_ids,
thus around 37000 names where damaged by the following programmatical
updates instead of only a hands full...
have you tested the query in psql?
as nothing to do
with the upper query so the upper query can return more than number of
rows specified in the subselect...
no clue which ones :-/
LIMIT is often meaningfull only in conjuction with ORDER BY
--
regards,
Jaime Casanova
"Programming today is a race between software engineer
s easy to
determine, in recent releases it's mandatory unless you specify the
opposite in postgresql.conf with the add_missing_from parameter
--
regards,
Jaime Casanova
"Programming today is a race between software engineers striving to
build bigger and better idiot-proof pr
iption:duplicate key violates unique constraint
Details:
the first thing you have to do is to upgrade at least to 7.4.13 (the
last release in that branch) and try again. Maybe the bug was already
fixed.
--
regards,
Jaime Casanova
"Programming today is a race between software engineers strivi
(GCC)
3.4.2 (mingw-special)
(1 fila)
pruebas=# select (1::float-1::float)*(-1);
?column?
--
0
(1 fila)
This is good for me... maybe a bug already fixed?
--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator ;)
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
The following bug has been logged online:
Bug reference: 2195
Logged by: Jaime Casanova
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.1
Operating system: Windows XP
Description:log_min_messages crash server when in DEBUG3 to 5
Details:
Hi,
in my machine
> instead of dd/mm/
> Please tell me how to fix this
> Thank you
>
Then, this is a pgAdmin bug and you have to report it to the pgAdmin team...
--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator ;)
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
wn issue, do it this way
CREATE OR REPLACE FUNCTION bugtest() RETURNS int AS
$BODY$
BEGIN
execute 'create temp table bugt(i int)';
execute 'insert into bugt values(1)';
execute 'drop table bugt';
RETURN 0;
END;
$BODY$
LANGUAGE 'plpgsql' VOLATILE;
--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator ;)
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
aboration or if..un has information agradeceria hug thanks
>
Sorry there is no spanglish list... please, post in english or in
spanish in [EMAIL PROTECTED] (i recommend you do that)
--
Atentamente,
Jaime Casanova
(DBA: DataBase Aniquilator ;)
---(end of broadcast)---
it in 8.1.1, so i guess you are right in tell that old
branches are broken...
--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator ;)
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an inde
tly on the column I will wait for the next release to
> test it (I don't have the source on my machine).
>
> BTW, I also observed the same behavior in 8.0.5 as well.
>
>
> John Supplee
>
of course. Tom backpatch all branches until 7.3...
--
regards,
Jaime Casanova
(DBA:
erver closed the connection unexpectedly
>
> Works for me as of 8.1 branch tip, so the fix is in either 8.1.1 or
> 8.1.2.
>
>regards, tom lane
>
must be in 8.1.2 because i'm saying the same error in 8.1.1
--
regards,
Jaime Casanova
(DBA: DataBase Aniqui
On 1/4/06, Michael Fuhr <[EMAIL PROTECTED]> wrote:
> On Wed, Jan 04, 2006 at 12:20:28PM -0500, Jaime Casanova wrote:
> > On 1/4/06, Brian Hirt <[EMAIL PROTECTED]> wrote:
> > > that's strange, because I'm running 8.1.1.
> >
> > what Tom i
ch to your tree source recompile
and you will have your problem solved now...
--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator ;)
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
structure.
>
> Please, help. I'll gladly provide any additional information as sonn as I
> know where to look.
>
> Robert
>
> PS. Spotting that kind of bug on production database (as it was i my case)
> can really spoil a day :)
>
Last year come up an issue with simil
uments, it works.
>
> Where am I wrong ?
>
> Thanks in advance for your help.
>
and... where is the function? how is defined? how do you use it?
code, please wiyhout that you can't expect any help...
--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator ;)
--
1 - 100 of 121 matches
Mail list logo
