On 1/04/2011 12:38 PM, Joshua D. Drake wrote:
On Fri, 2011-04-01 at 11:37 +0800, Craig Ringer wrote:
Many people have low-end SLR or high-end fixed cameras that're really
good video cameras, they just don't know it. Many of them will have
tripods, and a basic tripod for fixed indoor use is chea
On Fri, 2011-04-01 at 11:37 +0800, Craig Ringer wrote:
> Many people have low-end SLR or high-end fixed cameras that're really
> good video cameras, they just don't know it. Many of them will have
> tripods, and a basic tripod for fixed indoor use is cheap anyway.
>
> Given that, I wouldn't thi
On 22/03/2011 7:47 AM, Tomas Vondra wrote:
Dne 21.3.2011 20:23, Vick Khera napsal(a):
On Mon, Mar 21, 2011 at 1:45 PM, Aljoša Mohorović
wrote:
postgres is losing a lot of promotional and educational materials, why
is this happening?
Someone has to do lots of work to tape the talks, get pro
Hello!
In my current application I am sending a lot of data to/from the DB with
JDBC, and specifically arrays of Double. (or even Double[][]).
Alas, my current implementation I converts everything into a string
representation, which blows my memory out of the water and drops my
transaction rate way
On 03/31/2011 01:08 AM, Mike Orr wrote:
That might be a better solution. I was hoping to use the same pgdump
file for this that I also use for routine offline backup, but maybe
this is such a special case that a separate dump file would be better.
Why don't you post the exact mysqldump/mysql co
Not fully sure on the syntax of the Window to accomplish the specified goal
- and am not sure it would be any cleaner anyway.
But, the reason I am responding is how you phrased "...windows only compared
groups of records in the same table".
When I say:
FROM tableA
* JOIN tableB
I have now effec
On 03/31/2011 09:58 PM, Davi Duarte wrote:
Hello,
I'm using PL/Python in PostegreSQL 9.0.3 and Python 2.6.5, I want to use
a feature of Python 3, Python have an option to import a module from
future version of Python.
In my case, I want to use the Python 3 division module, because it
returns a
Once more, thanks!
Of course, using SERIAL is the ideal method, but I can't have the programs
in question fail because someone neglected to set up a dependency. Other
people may be slobs, but I'm afraid I can't be. In fact, my very first
attempt to use pg_get_serial_sequence(table_name, column_nam
On 03/31/2011 02:47 PM, Carlo Stonebanks wrote:
Thanks Adrian and Jerry.
Technically, the best way to know which sequence a column is dependent on is
to actually query for it. I have functions which query
information_schema.columns and run a regex_replace to extract the sequence
name from the de
Carlo Stonebanks writes:
> Thanks Adrian and Jerry.
>
> Technically, the best way to know which sequence a column is dependent on is
> to actually query for it. I have functions which query
> information_schema.columns and run a regex_replace to extract the sequence
> name from the defaulting nex
From a design standpoint, CHECK constraints are better than triggers in
general, and if it is possible to do what you want in a CHECK constraint, you
should choose that option, and leave triggers for other tasks that you can't use
CHECK for.
Or to put this a different way, triggers are the pro
Thanks Adrian and Jerry.
Technically, the best way to know which sequence a column is dependent on is
to actually query for it. I have functions which query
information_schema.columns and run a regex_replace to extract the sequence
name from the defaulting nextval() expression. This is better than
On 03/31/2011 02:13 PM, Jerry Sievers wrote:
Carlo Stonebanks writes:
Whenever I attempt to create a sequence whether this is done directly
via CREATE SEQUENCE or indrirectly vial declaring a column as SERIAL,
PG truncates it to 64 characters. Is this a documented limitation? I
cant find a ref
Carlo Stonebanks writes:
> Whenever I attempt to create a sequence whether this is done directly
> via CREATE SEQUENCE or indrirectly vial declaring a column as SERIAL,
> PG truncates it to 64 characters. Is this a documented limitation? I
> cant find a reference to it. Is it possible to change t
Whenever I attempt to create a sequence whether this is done directly via
CREATE SEQUENCE or indrirectly vial declaring a column as SERIAL, PG
truncates it to 64 characters. Is this a documented limitation? I can't find
a reference to it. Is it possible to change this limitation?
Our table nam
Whenever I attempt to create a sequence whether this is done directly via
CREATE SEQUENCE or indrirectly vial declaring a column as SERIAL, PG
truncates it to 64 characters. Is this a documented limitation? I can't find
a reference to it. Is it possible to change this limitation?
Our table nam
Hello,
I'm using PL/Python in PostegreSQL 9.0.3 and Python 2.6.5, I want to use a
feature of Python 3, Python have an option to import a module from future
version of Python.
In my case, I want to use the Python 3 division module, because it returns a
float division of integers by defaut, whi
Ya, I know I could pass them in. Just wanted to know if they were already
floating around out there as globals or something. That way I wouldn't have to
drop/recreate the constraint itself.
These would be constraint violations where the name of the constraint being
violated is in the return
"Gauthier, Dave" writes:
> I have a check constraint that runs a PlPgsql function which returns a
> pass/ fail status which the constraint uses to allow or disallow the
> value. This is not a trigger function. It's just a plain-ole
> PlPgsql. Is there a way I can read (not write, just read) th
On Thu, Mar 31, 2011 at 12:21:33PM -0700, babak badaei wrote:
> Hello Postgres Community,
>
> Thank you guys very much for PostgreSQL. To me, its the best database
> management system under the sun. I am setting up a new jail configuration
> on FreeBSD with sockets and everything enabled. I can
Hello Postgres Community,
Thank you guys very much for PostgreSQL. To me, its the best database
management system under the sun. I am setting up a new jail configuration
on FreeBSD with sockets and everything enabled. I can ping localhost fine. The
problem is that when I load a script that conn
Thanks. How would I do it with a window function? I thought windows
only compared groups of records in the same table.
On Thu, Mar 31, 2011 at 12:01 PM, David Johnston wrote:
> An alternative:
>
> SELECT
> parent.*,
> COALESCE(child.childcount, 0) AS whatever
> FROM parent
> LEFT JOIN
> (SELECT
On 03/31/2011 02:06 PM, Arjen Nienhuis wrote:
On Thu, Mar 31, 2011 at 20:05, Arjen Nienhuis wrote:
On Thu, Mar 31, 2011 at 18:56, Steve Clark wrote:
Hi List,
I am having a problem trying to do the following:
ssh postgres@192.168.198.93 'psql -Atc "select a.interface,
a.source_ip,a.dest_ip fr
An alternative:
SELECT
parent.*,
COALESCE(child.childcount, 0) AS whatever
FROM parent
LEFT JOIN
(SELECT parentid, count(*) as childcount FROM child GROUP BY parented) child
ON (parent.id = child.parentid)
You could also do:
SELECT parent.*,
COALESCE((SELECT count(*) FROM child WHERE child.id =
I know how to do count(*)/group by on a single table, but how do I get
a count of related records in a child table? Some of the counts will
be zero.
SELECT
parent.id AS id,
parent.name AS name,
parent.create_date AS create_date,
COUNT(child.id) AS count
FROM parent LEFT JOIN child
On 1 April 2011 05:16, Steve Crawford wrote:
> Well, to return to the original issue, should we allow the day to be spelled
> out and fix it (as noted in this thread it is non-standard but also
> unambiguous and we already allow plenty of non-standard formats) or throw an
> error? For me personall
I have a check constraint that runs a PlPgsql function which returns a
pass/fail status which the constraint uses to allow or disallow the value.
This is not a trigger function. It's just a plain-ole PlPgsql. Is there a way
I can read (not write, just read) the NEW.column values that a trigg
On 03/31/2011 10:51 AM, Brendan Jurd wrote:
I agree with your summary of the ISO standards. Unfortunately,
to_date and its cohorts are not targeting ISO. They are targeting
quasi-compatibility with some Oracle functions of the same name, I
suppose to make life easier for folks who are migratin
On Thu, Mar 31, 2011 at 20:05, Arjen Nienhuis wrote:
> On Thu, Mar 31, 2011 at 18:56, Steve Clark wrote:
>> Hi List,
>>
>> I am having a problem trying to do the following:
>> ssh postgres@192.168.198.93 'psql -Atc "select a.interface,
>> a.source_ip,a.dest_ip from kernel_gre a, ospfd_interface b
On Thu, Mar 31, 2011 at 18:56, Steve Clark wrote:
> Hi List,
>
> I am having a problem trying to do the following:
> ssh postgres@192.168.198.93 'psql -Atc "select a.interface,
> a.source_ip,a.dest_ip from kernel_gre a, ospfd_interface b where a.interface
> = b.interface and config ilike '%cost 50
t; 1. What we describe in the documentation as an ISO date is actually an ISO
> *week* date - a special purpose format included within ISO8601. 2011-03-31
> is also an ISO date as are 20110331, 20110331T013212 and
> 20110331T21.3344298. "Fixing" this is probably as simple as a clarif
Hello,
you are right I find one case in the query where I have infinite recursion
because the query result of
SELECT ev_class::regclass::text as relname
FROM pg_rewrite WHERE oid IN ( SELECT objid FROM pg_catalog.pg_depend
WHERE refobjid = xxx::regclass::oid AND deptype ='
ng of ISO formatting I see the following issues:
1. What we describe in the documentation as an ISO date is actually an
ISO *week* date - a special purpose format included within ISO8601.
2011-03-31 is also an ISO date as are 20110331, 20110331T013212 and
20110331T21.3344298. "Fixing" thi
Hi List,
I am having a problem trying to do the following:
ssh postgres@192.168.198.93 'psql -Atc "select a.interface, a.source_ip,a.dest_ip
from kernel_gre a, ospfd_interface b where a.interface = b.interface and config ilike
'%cost 50%';" config.db'
bash turns it into this:
ssh postgres@192.
On 1 April 2011 03:32, Adrian Klaver wrote:
> Now I am confused the docs say:
>
> D day of the week, Sunday(1) to Saturday(7)
> ID ISO day of the week, Monday(1) to Sunday(7)
>
> This would seem to say they both are one-based but differ on the day that is
> 1.
That's correct for the us
salah jubeh writes:
> Hello,
>
> I have written this function which is simply returns the entities which
> depends on a certain entity. It works fine if the
> dependency tree is not long. However, If I have an entity which are linked to
> many other entities I get
>
> stack depth limit exceeded
If you are working with Postgres version >= 8.4, you should look at the WITH
RECURSIVE (called recursive CTEs) feature:
http://www.postgresql.org/docs/8.4/static/queries-with.html
Regards,
On Thu, Mar 31, 2011 at 12:19 PM, salah jubeh wrote:
>
>
> Hello,
>
> I have written this function which
Hi All,
I would like to know about the best approach to take for providing a merged
model of libpq library. When I say "merged model" it means that the client
and server would be running as a single process. A single client libpq
application can be linked to either the client-server libpq librar
On 03/31/2011 08:27 AM, Brendan Jurd wrote:
On 1 April 2011 02:00, Adrian Klaver wrote:
On Wednesday, March 30, 2011 8:39:25 pm Brendan Jurd wrote:
If we wanted to make it "work", then I think the thing to do would be
to add a new set of formatting tokens IDY, IDAY etc. I don't like the
idea
Hello,
I have written this function which is simply returns the entities which depends
on a certain entity. It works fine if the dependency tree is not long. However,
If I have an entity which are linked to many other entities I get
stack depth limit exceeded
HINT: Increase the configurat
On 1 April 2011 02:35, Marc Munro wrote:
> Just to be clear, the reason I was mixing things in this way was that I
> wanted to validate that the dayname being passed was valid for the
> current locale, and I could find no easier way of doing it.
Ah, I see. In that case I think to_date would have
On Thu, 2011-03-31 at 08:00 -0700, Adrian Klaver wrote:
> On Wednesday, March 30, 2011 8:39:25 pm Brendan Jurd wrote:
> > On 31 March 2011 03:15, Steve Crawford
> > wrote:
> > > On 03/29/2011 04:24 PM, Adrian Klaver wrote:
> > >> ...
> > >> Well the strange part is only fails for SUN:...
[. . .]
On 1 April 2011 02:00, Adrian Klaver wrote:
> On Wednesday, March 30, 2011 8:39:25 pm Brendan Jurd wrote:
>> If we wanted to make it "work", then I think the thing to do would be
>> to add a new set of formatting tokens IDY, IDAY etc. I don't like the
>> idea of interpreting DY and co. differentl
On Wednesday, March 30, 2011 8:39:25 pm Brendan Jurd wrote:
> On 31 March 2011 03:15, Steve Crawford wrote:
> > On 03/29/2011 04:24 PM, Adrian Klaver wrote:
> >> ...
> >> Well the strange part is only fails for SUN:...
> >> test(5432)aklaver=>select to_date('2011-13-SUN', 'IYYY-IW-DY');
> >> to_
Thanks to all.
I found the wrong configuration in pg_hba.conf. The problem is solved.
On Tue, Mar 29, 2011 at 8:02 PM, Raymond O'Donnell wrote:
> On 29/03/2011 14:59, Kalai R wrote:
>
>> Hi,
>> I am using Windows XP. When I have installed PostgreSQL 9.0.3, the
>> service didn't start automatica
> Yes, but its more than fsync.
>
> You'd need to copy the whole table, all indexes and forks to WAL if
> wal_level is set high.
"if" wal_level is set high. If it's set to minimal it would be "simple" fsyncs,
right? I mean: if it's at minimal it wouldn't take long, and it basically won't
re-wr
On Thu, Mar 31, 2011 at 12:24 PM, Leonardo Francalanci wrote:
>> I suppose that a similar effect could be achieved by something like
>>
>> CREATE TABLE mytable_logged AS
>> SELECT * FROM mytable_unlogged;
>>
>> which would not produce WAL:
>
>
> yes, but it would mean re-writing the whole da
> I suppose that a similar effect could be achieved by something like
>
> CREATE TABLE mytable_logged AS
> SELECT * FROM mytable_unlogged;
>
> which would not produce WAL:
yes, but it would mean re-writing the whole data + re-creating the indexes.
I didn't know that some statements don't
Hi,
Although I finally managed to build libpq using Visual C++, I'm
continuously experiencing problems with this IDE.
Therefore I switched to MinGW and it was indeed easy to compile libpq
with it from the first time on.
However, I'm experiencing the same problem as discussed on
http://archives
On Thu, Mar 31, 2011 at 08:57:09AM +0100, Leonardo Francalanci wrote:
> Hi,
>
> we're inserting tons of rows in some partitioned tables, and to get
> more performance out of the system we would like to use UNLOGGED
> tables that, after some time, become "regular" tables (at that point, we
> wouldn
Hi,
we're inserting tons of rows in some partitioned tables, and to get
more performance out of the system we would like to use UNLOGGED
tables that, after some time, become "regular" tables (at that point, we
wouldn't want to write to them anymore; we could only select or drop
them). Would it be
51 matches
Mail list logo
