hubert depesz lubaczewski writes:
> basically - shouldn't this command raise error instead of creating index
> named "concurrently"?
No. That would mean that "concurrently" is a reserved word.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql
well, the question is in subject.
basically - shouldn't this command raise error instead of creating index
named "concurrently"?
depesz
--
Linkedin: http://www.linkedin.com/in/depesz / blog: http://www.depesz.com/
jid/gtalk: dep...@depesz.com / aim:depeszhdl / skype:depesz_hdl / gg:6749007
-
buenas tardes
estoy tratando de instalar postgresql 8.2 pero en la parte "initialise
databasecluster" cuando ingreso un el password al dar next>> me sale el
siguiente mensaje:
the "secondary logon" service is not running. this service is required for the
installer to initi
Craig Ringer wrote:
On Tue, 2009-09-15 at 19:26 +, Joseph Shraibman wrote:
The following bug has been logged online:
While the test case is appreciated, it's not really that clear what's
expected to happen vs what happens, at what point things go wrong and
under what circumstances, etc. L
Robert Haas writes:
> On Thu, Sep 17, 2009 at 10:44 AM, Andre Rothe wrote:
>> The problem is, that I get the default values from a metadata query
>> with JDBC,
>> so I have to parse every return value for such an annotation before I
>> can use them.
> That sounds annoying, but it's not a Postgre
On Thu, Sep 17, 2009 at 10:44 AM, Andre Rothe wrote:
> The problem is, that I get the default values from a metadata query
> with JDBC,
> so I have to parse every return value for such an annotation before I
> can
> use them.
That sounds annoying, but it's not a PostgreSQL bug.
> So it seems tha
Jeff Davis wrote:
> To reproduce:
>
> 1. initdb -D data
> 2. cat /dev/null > data/postgresql.conf
> 3. pg_ctl -w -D data start
>
> I attached a quick patch that seems to do the trick. It appears that
> fgets() will always return non-NULL if the size passed in is 1 (i.e.
> maxlength in the caller
The problem is, that I get the default values from a metadata query
with JDBC,
so I have to parse every return value for such an annotation before I
can
use them.
So it seems that I could change the jdbc driver to a newer version. I
use the
PostgreSQL 8.1 JDBC3 with SSL (build 407).
Thanks
Andre
"philip wright" writes:
> Description:8.4.1 compile fails on debian can't find libdl
Our Debian packager would certainly have complained before now if PG
didn't build on Debian. I suspect that you have forgotten to install
some needed support files. Does Debian have the equivalent of -d
there is a database running on xen dom U, but the node (dom0) went down,
we have a cluster, so the other node started the service and there is
nothing that shows any problem
unless i use SELECT on this database/table (this db contains only one table)
there is no backup of the database.
i can't see
The following bug has been logged online:
Bug reference: 5062
Logged by: philip wright
Email address: z...@de1.uga.duke.edu
PostgreSQL version: 8.4.1
Operating system: Linux Debian Debian 4.1.2-25
Description:8.4.1 compile fails on debian can't find libdl
Details:
.
On Thu, Sep 17, 2009 at 8:15 AM, Andre Rothe wrote:
> Hi,
>
> I have installed Postgres 8.3.8 on Fedora Linux. If I create a table,
> the default values will be set by the database to
>
> NULL::timestamp without time zone
>
> for a timezone column and to
>
> NULL::character varying
>
> for a varch
Hi,
I have installed Postgres 8.3.8 on Fedora Linux. If I create a table,
the default values will be set by the database to
NULL::timestamp without time zone
for a timezone column and to
NULL::character varying
for a varchar column. How I can prevent such a behaviour? Both column
defaults shou
13 matches
Mail list logo
