On Jun 28, 2013, at 8:10, Vincent Veyron wrote:
> Hi,
>
> FYI, I had the exact same problem earlier this week, while building a
> new Debian Stable (Wheezy) server where postgresql version is 9.1.9-1
> for a database containing accented characters.
You probably had a rather different problem,
I forgot to mention that the machines use an amd64 processor.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Hello
2013/6/28 Vincent Veyron :
> Hi,
>
> FYI, I had the exact same problem earlier this week, while building a
> new Debian Stable (Wheezy) server where postgresql version is 9.1.9-1
> for a database containing accented characters.
>
> Steps where :
> pg_dump of a database encoded in LATIN9 on t
Hi,
FYI, I had the exact same problem earlier this week, while building a
new Debian Stable (Wheezy) server where postgresql version is 9.1.9-1
for a database containing accented characters.
Steps where :
pg_dump of a database encoded in LATIN9 on the old machine which uses
the fr_FR@euro locale
>I've done something weird:
>CREATE OR REPLACE FUNCTION "timestamp"(_date date, _time time) RETURNS
timestamp AS $$
>SELECT _date + _time;
>$$ LANGUAGE sql;
>SELECT "timestamp"('2013-01-01'::date, '12:00:00'::time);
Good one.
function with above definition is already present in pg_catalog. so n
Using your link
http://www.postgresql.org/docs/9.2/static/functions-formatting.html
In DB2 when I use following command I am getting output combined date and
time i passed to function.
#SELECT TIMESTAMP('2013-01-01','12:13:14') FROM SYSIBM.SYSDUMMY1
1
---
I have something that I think is a fairly common code model, but with
an SQL query that feels like it's fighting the system.
The 'cron' table has a number of tasks (one row = one task), and the
primary loop of the program (massively simplified) fetches one row,
processes it, commits. One row/task
Works like a charm :)
thanks a lot.
Regards,
Bartek
2013/6/27 Pavel Stehule
> Hello
>
>
> 2013/6/27 Bartosz Dmytrak :
> > Hi All
> > Let's assume I've got 3 tables:
> >
> > "OrgStructure"."tblUnits",
> > "OrgStructure"."tblUnitStructure",
> > "Dictionary"."tblUnits"
> >
> > I would like to do
Hello
2013/6/27 Bartosz Dmytrak :
> Hi All
> Let's assume I've got 3 tables:
>
> "OrgStructure"."tblUnits",
> "OrgStructure"."tblUnitStructure",
> "Dictionary"."tblUnits"
>
> I would like to do the EXPLAIN:
> EXPLAIN
> SELECT * FROM "OrgStructure"."tblUnits", "OrgStructure"."tblUnitStructure",
>
Hi All
Let's assume I've got 3 tables:
- "OrgStructure"."tblUnits",
- "OrgStructure"."tblUnitStructure",
- "Dictionary"."tblUnits"
I would like to do the EXPLAIN:
EXPLAIN
SELECT * FROM "OrgStructure"."tblUnits", "OrgStructure"."tblUnitStructure",
"Dictionary"."tblUnits"
(Of course its ca
On Thu, Jun 27, 2013 at 4:58 AM, Sandro Santilli wrote:
> According to release notes of 8.3.18 (yeah, old docs)
> a trigger runs with the the table owner permission.
>
> This is the only document I found about this matter:
> http://www.postgresql.org/docs/8.3/static/release-8-3-18.html
>
>
> Requ
On 6/27/2013 4:51 AM, sachin kotwal wrote:
#select timestamp(current_date);
try... current_date::timestamptz
orcast current_date as timestamptz
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-general maili
On 6/27/2013 6:44 AM, Igor Neyman wrote:
Try to look at Windows Event Log, m.b. there will be some useful info.
nada but unrelated noise
M.b. you need to run installer local (not corporate active directory) account,
still member of local Administrators group.
hmmm. having local accounts
I found out what was happening. When the path variables were manually set,
something in build.pl was overwriting 64 bit to 32 bit (not sure why. The build
was saying 64 was detected and will be used, but then many files were being
compiled as 32 bit).
I used a cmd prompt that came with Msft vs
Merlin Moncure wrote:
>
> json deserialization was heavily enhanced in the upcoming 9.3 release
> which would make dealing with this triival. for now, you have to
> fire up pl/v8 or another pl with heavy json support or implement a
> crude parser in sql :/
http://www.pgxn.org/dist/json_enhanc
> -Original Message-
> From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-
> ow...@postgresql.org] On Behalf Of John R Pierce
> Sent: Wednesday, June 26, 2013 4:13 PM
> To: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] installer woes, 9.1 on windows 2008 R2
>
> On 6/2
On 2013-06-27 20:43, sachin kotwal wrote:
While migrating my application from DB2 to PostgreSQL.
I want to migrate TIMESTAMP() function of DB2 into PostgreSQL.
Example in DB2:
#SELECT TIMESTAMP('2013-01-01','12:13:14') FROM SYSIBM.SYSDUMMY1
1
--
2013-01-01-12.13.14.
In my development environment, I am using the auto_explain module to help debug
queries the developers complain about being slow. I am also using the
oracle_fdw to perform queries against some oracle servers. These queries are
generally very slow and the application allows them to be. The troubl
I've done something weird:
CREATE OR REPLACE FUNCTION "timestamp"(_date date, _time time) RETURNS
timestamp AS $$
SELECT _date + _time;
$$ LANGUAGE sql;
SELECT "timestamp"('2013-01-01'::date, '12:00:00'::time);
It worked, but you will need explict cast and quote the timestamp function
name... M
According to release notes of 8.3.18 (yeah, old docs)
a trigger runs with the the table owner permission.
This is the only document I found about this matter:
http://www.postgresql.org/docs/8.3/static/release-8-3-18.html
Require execute permission on the trigger function for CREATE TRIGGER (Rob
On 27/06/2013 12:51, sachin kotwal wrote:
> I have done some more try as follows:
>
> #select timestamp(current_date);
> ERROR: syntax error at or near "current_date" at character 18
> STATEMENT: select timestamp(current_date);
> ERROR: syntax error at or near "current_date"
> LINE 1: select ti
I have done some more try as follows:
#select timestamp(current_date);
ERROR: syntax error at or near "current_date" at character 18
STATEMENT: select timestamp(current_date);
ERROR: syntax error at or near "current_date"
LINE 1: select timestamp(current_date);
=
While migrating my application from DB2 to PostgreSQL.
I want to migrate TIMESTAMP() function of DB2 into PostgreSQL.
Example in DB2:
#SELECT TIMESTAMP('2013-01-01','12:13:14') FROM SYSIBM.SYSDUMMY1
1
--
2013-01-01-12.13.14.00
1 record(s)
On Wed, Jun 26, 2013 at 3:47 AM, James Sewell wrote:
> Hello All,
>
> Is there a way to disable chasing LDAP referrals in PostgreSQL?
>
There is not, at this point. It would probably be fairly trivial to add a
pg_hba parameter to turn it off (since it's, AFAIK, just a call to
ldap_set_option), bu
24 matches
Mail list logo
