On Jan 14, 2008, at 3:58 AM, pepone.onrez wrote:
I have this query in a table with 150 thowsand tuples and it takes
to long
t_documentcontent._id AS _id
FROM t_documentcontent LIMIT 50 OFFSET 8
You want an ORDER BY there. Not only will it probably speed things
up, without it
Hi all.
Is there a way with the libpq to access subcolumns in a composite type
column?
The documentation (8.2) seems not to mention this case.
Thanks.
--
Reg me, please!
---(end of broadcast)---
TIP 4: Have you searched our list archives?
On Jan 15, 2008, at 3:03 PM, Ivan Sergio Borgonovo wrote:
On Tue, 15 Jan 2008 14:43:35 +0100
Alban Hertroys [EMAIL PROTECTED] wrote:
You need to scroll to the last row to find the size of the result
set, but after that it's pretty easy to return random rows by
scrolling to them (and marking
Hi,
Some days ago we were having problems running pg_dump (v. 8.2.5.7260) from
Windows XP SP2 to a database in a sever PostgreSQL 8.2.5 on
amd64-portbld-freebsd6.2.
We thought the problem was solved but we are having problems again.
Now we got an error:
cannot allocate memory for input buffer
On Tue, Jan 15, 2008 at 04:49:41PM -0600, Scott Marlowe wrote:
This query is not capable of using an index on name, since you can't
use an index with a like beginning with a %... So
actually you can. you just can't use index for like %something%, but it
can be solved using trigrams or another
Sebastián Baioni wrote:
Hi,
Some days ago we were having problems running pg_dump (v. 8.2.5.7260) from
Windows XP SP2 to a database in a sever PostgreSQL 8.2.5 on
amd64-portbld-freebsd6.2.
We thought the problem was solved but we are having problems again.
Now we got an error:
cannot allocate
This looks like an endianess mismatch; did you already mention on
what
architecture you are on?
MacPro, Leopard
Did you just move from a PPC-based Mac to an Intel-based one?
If so, you're out of luck --- you need to go back to the PPC
to make a dump of those files.
No, I just
--- Richard Huxton [EMAIL PROTECTED] escribió:
Sebastián Baioni wrote:
Hi,
Some days ago we were having problems running pg_dump (v. 8.2.5.7260) from
Windows XP SP2 to a
database in a sever PostgreSQL 8.2.5 on amd64-portbld-freebsd6.2.
We thought the problem was solved but we are
--- Sebastián Baioni [EMAIL PROTECTED] escribió:
--- Richard Huxton [EMAIL PROTECTED] escribió:
Sebastián Baioni wrote:
Hi,
Some days ago we were having problems running pg_dump (v. 8.2.5.7260)
from Windows XP SP2 to
a
database in a sever PostgreSQL 8.2.5 on
Unfortuantely, there is no way around it.
Without cascade it won't let you delete the schema or table.
Functions will not be dropped.
Sim
Peter Bauer wrote:
Hi all,
i made some views for the slony1 configuration tables in the public schema
which refer to tables in the _slony1 schema. My
Hi all,
i made some views for the slony1 configuration tables in the public schema
which refer to tables in the _slony1 schema. My problem now is that if the
_slony1 schema is dropped with cascade or slony is uninstalled, these views
are also dropped and i have to recreate them if slony is
On Thu, January 17, 2008 10:15, Scott Marlowe wrote:
If race conditions are a possible issue, you use a sequence and
increment that until you get a number that isn't used. That way two
clients connecting at the same time can get different, available
numbers.
That is close to the idea that
On Jan 17, 2008 9:05 AM, James B. Byrne [EMAIL PROTECTED] wrote:
If the entries involved numbered in the millions then Scott's approach has
considerable merit. In my case, as the rate of additions is very low and
the size of the existing blocks is in the hundreds rather than hundreds of
Sebastián Baioni wrote:
I contacted the Admin and told me there was no erros nor in the
postgresql log nor in the server log.
I forgot to tell that the error was seen on the client but it was a
response from the server: pg_dump: Mensaje de error del servidor:
cannot allocate memory for input
=?iso-8859-1?q?Sebasti=E1n=20Baioni?= [EMAIL PROTECTED] writes:
I forgot to tell that the error was seen on the client but it was a response
from the server:
pg_dump: Mensaje de error del servidor: cannot allocate memory for input
buffer
pg_dump: El comando es: COPY public.sipat00
Reg Me Please [EMAIL PROTECTED] writes:
Is there a way with the libpq to access subcolumns in a composite type
column?
libpq knows nothing in particular about composite columns. You'd need
to parse out the data for yourself, per the syntax rules at
Joshua D. Drake wrote:
Robert Treat wrote:
There's been a big move in the php community to push people towards
php5 (one of which was EOL of php4), which has started to pay off.
I'd guess that if they wanted to, they could switch to PDO with
Drupal 7 and not hurt themselves too much.
When
On Wed, January 16, 2008 18:40, Scott Marlowe wrote:
You're essentially wanting to fill in the blanks here. If you need
good performance, then what you'll need to do is to preallocate all
the numbers that haven't been assigned somewhere. So, we make a table
something like:
create table
On Jan 17, 2008 9:19 AM, James B. Byrne [EMAIL PROTECTED] wrote:
On Thu, January 17, 2008 10:15, Scott Marlowe wrote:
If race conditions are a possible issue, you use a sequence and
increment that until you get a number that isn't used. That way two
clients connecting at the same time
In response to Tom Hart [EMAIL PROTECTED]:
Joshua D. Drake wrote:
Robert Treat wrote:
There's been a big move in the php community to push people towards
php5 (one of which was EOL of php4), which has started to pay off.
I'd guess that if they wanted to, they could switch to PDO
Hello List,
I am doing a pg_dumpall -c on 7.4.
I then use psql to load into 8.2 everything seems to be right except my
db user passwords don't work anymore.
What am I missing.
I have already tried starting 8.2 postgres with both
#password_encryption = on
password_encryption = off
then
On Jan 17, 2008 9:19 AM, James B. Byrne [EMAIL PROTECTED] wrote:
On Thu, January 17, 2008 10:15, Scott Marlowe wrote:
If race conditions are a possible issue, you use a sequence and
increment that until you get a number that isn't used. That way two
clients connecting at the same time
Hello List,
the man page for pg_dump say:
pg_dump is a utility for backing up a PostgreSQL database. It makes
consistent backups even if the database is being used
concurrently.
does pg_dumpall make consistent backups if the database is being used
concurrently?
Even though
On Jan 17, 2008 10:35 AM, Steve Clark [EMAIL PROTECTED] wrote:
Hello List,
I am doing a pg_dumpall -c on 7.4.
I then use psql to load into 8.2 everything seems to be right except my
db user passwords don't work anymore.
What am I missing.
What error message are you getting?
On Thu, Jan 17, 2008 at 11:14:22AM -0800, Glyn Astill wrote:
begin;
set transaction isolation level serializable;
--- begin dumping stuff;
Wouldn't that just lock everything so nothing could be updated? Or
just the table it is outputting?
PostgreSQL uses MVCC, which means the
Alvaro Herrera [EMAIL PROTECTED] wrote:
Glyn Astill wrote:
Out of interest, how does pg_dump manage to do a snapshot of a
database at an instant in time?
My mental picture of pg_dump was just a series of queries dumping
out
the tables...
begin;
set transaction isolation level
On Thu, 17 Jan 2008, Tom Lane wrote:
There isn't any good way to guarantee time coherence of dumps across two
databases.
Whether there's a good way depends on what you're already doing. If
you're going to the trouble of making a backup using PITR anyway, it's not
hard to stop applying new
Scott Marlowe wrote:
On Jan 17, 2008 10:35 AM, Steve Clark [EMAIL PROTECTED] wrote:
Hello List,
I am doing a pg_dumpall -c on 7.4.
I then use psql to load into 8.2 everything seems to be right except my
db user passwords don't work anymore.
What am I missing.
What error message are you
On Jan 17, 2008, at 8:27 AM, Sim Zacks wrote:
Peter Bauer wrote:
Hi all,
i made some views for the slony1 configuration tables in the
public schema which refer to tables in the _slony1 schema. My
problem now is that if the _slony1 schema is dropped with cascade
or slony is uninstalled,
Out of interest, how does pg_dump manage to do a snapshot of a
database at an instant in time?
My mental picture of pg_dump was just a series of queries dumping out
the tables...
--- Tom Lane [EMAIL PROTECTED] wrote:
Steve Clark [EMAIL PROTECTED] writes:
does pg_dumpall make consistent
Tom Lane wrote:
Steve Clark [EMAIL PROTECTED] writes:
does pg_dumpall make consistent backups if the database is being used
concurrently?
Even though the man page doesn't say it does.
That's intentional, because it doesn't. What you get is a pg_dump
snapshot of each database in
Hello! This is just a test, please ignore.
If you don't ignore it, I'll ignore you.
Thanks,
--
Alvaro Herrera
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to
Steve Clark [EMAIL PROTECTED] writes:
does pg_dumpall make consistent backups if the database is being used
concurrently?
Even though the man page doesn't say it does.
That's intentional, because it doesn't. What you get is a pg_dump
snapshot of each database in sequence; those snapshots
On Jan 17, 2008, at 1:08 PM, Greg Smith wrote:
On Thu, 17 Jan 2008, Tom Lane wrote:
There isn't any good way to guarantee time coherence of dumps
across two databases.
Whether there's a good way depends on what you're already doing.
If you're going to the trouble of making a backup
Bill Moran wrote:
In response to Tom Hart [EMAIL PROTECTED]:
Let me just sneak in a quick rant here, from somebody who really doesn't
matter.
We run drupal for our corporate intranet (currently being built) and we
use postgreSQL as the backend. Some of the modules and things don't work
On Thu, Jan 17, 2008 at 11:10:25AM -0600, Erik Jones wrote:
If you dropped tables out from under views, how would you expect them
to act if someone were to query them? Inconsistent and unpredictable
are just two words I'd use to describe a system that allowed that.
I'd expect it to
Glyn Astill wrote:
Out of interest, how does pg_dump manage to do a snapshot of a
database at an instant in time?
My mental picture of pg_dump was just a series of queries dumping out
the tables...
begin;
set transaction isolation level serializable;
--- begin dumping stuff;
--
Alvaro
Alvaro Herrera [EMAIL PROTECTED] writes:
Tom Lane wrote:
That's intentional, because it doesn't. What you get is a pg_dump
snapshot of each database in sequence; those snapshots don't all
correspond to the same time instant. There isn't any good way to
guarantee time coherence of dumps
We have a machine that serves as a fileserver and a database server. Our
server hosts a raid array of 40 disk drives, attached to two3-ware cards,
one 9640SE-24 and one 9640SE-16. We have noticed that activity on one
controller blocks access on the second controller, not only for disk-IO but
also
On Thu, 17 Jan 2008 11:03:43 -0500
Tom Hart [EMAIL PROTECTED] wrote:
Let me just sneak in a quick rant here, from somebody who really
doesn't matter.
We run drupal for our corporate intranet (currently being built)
and we use postgreSQL as the backend. Some of the modules and
things don't
Hello,
someone can tell me if is secure to create external python modules and
import them to functions/procedures/triggers to use?
I am doing the following:
function/procedure/trigger:
CREATE OR REPLACE FUNCTION tabela_be_i_tg_fx() RETURNS trigger AS $body$
from dbfunctions.postgres.pg_trigger
On Jan 17, 2008 1:43 PM, Tom Hart [EMAIL PROTECTED] wrote:
Obviously emotion has gotten the better of me which is why I won't post
to the drupal boards/lists
Really, honestly, you're controlling it quite well. Passion is fine.
As long as the lists stay civil, passion has its place.
(I might
In response to Tom Hart [EMAIL PROTECTED]:
Bill Moran wrote:
[snip]
To a large degree, I think Karoly has blown the situation out of
proportion. Look at how it affects _this_ list every time he starts
bitching, for example.
Is it just Karoly (chx) who has all these things to say
I evaluated Drupal with PostgreSQL, but it wasn't powerful enough, and it's
written in PHP which is buggy, and lots of modules force you to use MySQL
which is not ACID (I'm sorry but inserting 31-Feb-2008 and not throwing an
error by default makes you non-ACID in my book). PostgreSQL support was
On Thu, 17 Jan 2008 15:52:37 -0500
Alex Turner [EMAIL PROTECTED] wrote:
I evaluated Drupal with PostgreSQL, but it wasn't powerful enough,
and it's written in PHP which is buggy, and lots of modules force
you to use MySQL which is not ACID (I'm sorry but inserting
31-Feb-2008 and not throwing
At 4:11p -0500 on 17 Jan 2008, Bill Moran wrote:
The guy sets my jerk alarms ringing like a 5 alarm fire. He doesn't
play well with others, he constantly starts fights, and he threatens
to take his ball and go home every time he loses. I don't care how
much code he writes, I don't think he's
Janine Sisk [EMAIL PROTECTED] writes:
But I'm still getting this error when loading the data into the new
database:
ERROR: invalid byte sequence for encoding UTF8: 0xeda7a1
The reason PG doesn't like this sequence is that it corresponds to
a Unicode surrogate pair code point, which is not
After discovering that pg_get_serial_sequence behaves in a bit
strange way[1] when it deals to case sensitiveness... I just
discovered that you've the same behaviour for any function... at
least in PHP.
postgresql
Versione: 8.1.11
php:
Versione: 5.2.0
eg.
create or replace function testA(out
On Jan 17, 2008 5:48 AM, Reg Me Please [EMAIL PROTECTED] wrote:
Hi all.
Is there a way with the libpq to access subcolumns in a composite type
column?
The documentation (8.2) seems not to mention this case.
Thanks.
--
We have a proposal to do this for 8.4. We will probably maintain this
Ivan Sergio Borgonovo [EMAIL PROTECTED] writes:
After discovering that pg_get_serial_sequence behaves in a bit
strange way[1] when it deals to case sensitiveness
The SQL standard specifies that unquoted identifiers are case-insensitive.
You're welcome to spell them as camelCase in your source
Hi all,
I'm moving a database from PG 7.2.4 to 8.2.6. I have already run
iconv on the dump file like so:
iconv -c -f UTF-8 -t UTF-8 -o out.dmp in.dmp
But I'm still getting this error when loading the data into the new
database:
ERROR: invalid byte sequence for encoding UTF8: 0xeda7a1
On Thu, 17 Jan 2008 19:07:59 -0500
Tom Lane [EMAIL PROTECTED] wrote:
Ivan Sergio Borgonovo [EMAIL PROTECTED] writes:
After discovering that pg_get_serial_sequence behaves in a bit
strange way[1] when it deals to case sensitiveness
The SQL standard specifies that unquoted identifiers are
On Thu, January 17, 2008 11:48, Scott Marlowe wrote:
Got bored, hacked this aggregious pl/pgsql routine up. It looks
horrible, but I wanted it to be able to use indexes. Seems to work.
Test has ~750k rows and returns in it and returns a new id in 1ms
on my little server.
File attached.
This looks like an endianess mismatch; did you already mention on
what
architecture you are on?
MacPro, Leopard
Did you just move from a PPC-based Mac to an Intel-based one?
If so, you're out of luck --- you need to go back to the PPC
to make a dump of those files.
No, I just
Just wondering if my 'Perceived' feeling that since implementing slony
for master/slave replication of select tables, my master database
performance is getting slower.
I'm constantly seeing a very high amount of IO wait. ~40-80 according to
vmstat 1
and according to atop. (hdb/hdc = raid1
On jeu, 2008-01-17 at 21:25 +0100, Ivan Sergio Borgonovo wrote:
Joshua posted the link to Edison's project that can support pg, MS
SQL, Oracle, DB2(?)... but well I had the feeling that Edison is a bit
ostracised. While I wouldn't define his work a DB AL... well it works
so kudos!
56 matches
Mail list logo
