Hi all,
I've run pgbench with a scale of 2000, and have noticed that the %
done goes a bit wonky:
thom@bison:~$ pgbench -i -s 2000 pgbench
NOTICE: table "pgbench_history" does not exist, skipping
NOTICE: table "pgbench_tellers" does not exist, skipping
NOTICE: table "pgbench_accounts" does not
Hi,
I have noticed that, using pg_ctl, if you start Postgres using a
relative path, then attempt to restart it from anywhere else, it
fails.
Example:
thom@swift /tmp $ pg_ctl -D primary start
server starting
thom@swift /tmp $ pg_ctl -D primary restart
waiting for server to shut down done
ser
On 15 August 2012 16:30, Tom Lane wrote:
> Thom Brown writes:
>> On 12 August 2012 08:17, Thom Brown wrote:
>>> On 12 August 2012 01:06, Tom Lane wrote:
>>>> ISTM we ought to disallow that ... either the schema is inside the
>>>> extension, or
On 12 August 2012 08:17, Thom Brown wrote:
> On 12 August 2012 01:06, Tom Lane wrote:
>> Thom Brown writes:
>>> I'm getting a dependency loop issue with pg_dump when adding a schema
>>> to an extension where the schema being added is the same as the
On 12 August 2012 01:06, Tom Lane wrote:
> Thom Brown writes:
>> I'm getting a dependency loop issue with pg_dump when adding a schema
>> to an extension where the schema being added is the same as the one
>> containing the extension.
>
>> CREATE EXTENSION fi
Hi,
I'm getting a dependency loop issue with pg_dump when adding a schema
to an extension where the schema being added is the same as the one
containing the extension.
CREATE EXTENSION file_fdw;
ALTER EXTENSION file_fdw ADD SCHEMA public;
$ pg_dump -f /dev/null test
pg_dump: [sorter] WARNING: co
ation statement runs. If creating the same 2 tables without
originally giving them primary keys, this rule creates successfully.
--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On 21 January 2011 14:55, Bernd Helmle wrote:
>
>
> --On 20. Januar 2011 21:56:44 +0000 Thom Brown wrote:
>
>>> Known bug in OSX's libedit. Use readline instead.
>>>
>>> http://archives.postgresql.org/pgsql-bugs/2010-04/msg00127.php
>>>
>
On 20 January 2011 21:44, Tom Lane wrote:
> Thom Brown writes:
>> postgres=# \d pg_opsql(29265) malloc: *** error for object 0x5:
>> pointer being freed was not allocated
>> *** set a breakpoint in malloc_error_break to debug
>> Abort trap
>
>> System info:
&g
Intel Core i5 2.53 Ghz
Memory: 2x2GB DDR3 @ 1066Mhz
Built with GNU Make 3.81
GCC version: i686-apple-darwin10-gcc-4.2.1
If required, I can provide the configure output.
--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935
--
Sent via pgsql-bugs mailing l
tion when they do this.
>
> It confuses the shit out of me. It says "string_agg(text)" doesn't exist when
> that clearly is not the name of the function you've called.
>
What function name do you believe was called?
--
Thom Brown
Registered Linux user: #516935
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ATES
It's clear as day upon reading that. It's a case of one page reading:
string_agg(expression [, delimiter ] )
and another reading:
aggregate_name (expression [ , ... ] [ order_by_clause ] )
and you effectively end up with:
string_agg(expression [, delimiter ] [ order_by_cl
regate call and ORDER BY clause.
>>
>
> What syntax is that?
>
> --
> greg
>
An example I've found is:
SELECT deptno, LISTAGG(ename, ',') WITHIN GROUP (ORDER BY ename) AS employees
FROM emp
GROUP BY deptno;
--
Thom Brown
Registered Linux user: #516935
--
change their vote after seeing the patch?
>
> regards, tom lane
>
>
I was afraid that the function would be pulled completely, but from
looking at the patch, you're only removing the function with a
single-parameter signature, which is quite innocuous. So I&
ng of pg_upgrade due to the
> initdbs and otherwise. I think 9.0 is going to have a pretty darned
> solid pg_upgrade because of it.
>
Leave my name off the commit comment then ;) People who have been
waiting for this will burn me as a heretical witch... er.. man
witch... warlock?
--
Thom
how it is. It only needed
clarification in the documentation to explain its usage for the
scenario in question, and probably a couple entries in the regression
tests as they're lacking at the moment.
I wish I had held back on mentioning it as I remembered later that
this has already been dis
On 4 August 2010 14:24, Pavel Stehule wrote:
> 2010/8/4 Thom Brown :
>> On 4 August 2010 14:04, Robert Haas wrote:
>>> On Wed, Aug 4, 2010 at 6:03 AM, Thom Brown wrote:
>>>> Actually, this rings a bell. I think this may have been raised
>>>> before
On 4 August 2010 14:04, Robert Haas wrote:
> On Wed, Aug 4, 2010 at 6:03 AM, Thom Brown wrote:
>> Actually, this rings a bell. I think this may have been raised
>> before, something to do with the delimiter being accepted as one of
>> the order by values. If this isn&
On 4 August 2010 10:44, Thom Brown wrote:
> On 4 August 2010 10:36, Thom Brown wrote:
>> I'd like to report a potential bug (or just my misunderstanding), but
>> I couldn't find any mention in the TODO or on the mailing list.
>>
>> I'm using PostgreSQ
On 4 August 2010 10:36, Thom Brown wrote:
> I'd like to report a potential bug (or just my misunderstanding), but
> I couldn't find any mention in the TODO or on the mailing list.
>
> I'm using PostgreSQL 9.0 beta 3 on Gentoo x64 (sorry, I don't have
> beta 4 y
1 | meow,bark
(1 row)
The reason I expect this to work is because of what is stated in the
documentation:
http://www.postgresql.org/docs/9.0/static/functions-aggregate.html
"This ordering is unspecified by default, but can be controlled by
writing an ORDER BY clause within the aggregate cal
On 10 June 2010 17:48, Alvaro Herrera wrote:
> Excerpts from Thom Brown's message of jue jun 10 12:20:57 -0400 2010:
>> On 10 June 2010 16:48, Tom Lane wrote:
>> > Thom Brown writes:
>> >> On 10 June 2010 15:34, Tom Lane wrote:
>> >>> You nee
On 10 June 2010 16:48, Tom Lane wrote:
> Thom Brown writes:
>> On 10 June 2010 15:34, Tom Lane wrote:
>>> You need to look into why configure failed to detect that your platform
>>> has unsetenv.
>
>> Is that heimdal_strlcpy patch normal too?
>
> Sor
On 10 June 2010 15:34, Tom Lane wrote:
> Thom Brown writes:
>> In file included from ../../src/include/c.h:851,
>> from crypt.c:44:
>> ../../src/include/port.h:392: error: expected identifier or '(' before
>> '__extension__'
>
Not sure where this needed to be posted, so guessing it's supposed to be here?
I've attempted to emerge beta 2 in Gentoo x64 with a 2.6.31-xen-r12
kernel, but it outputs the following:
# less /var/tmp/portage/dev-db/postgresql-base-9.0_beta2/temp/build.log
* CPV: dev-db/postgresql-base-9.0_beta
On 27 May 2010 23:00, Tom Lane wrote:
> Thom Brown writes:
>> This probably isn't a legitimate bug, but as a precaution
>> I'm running the following command against PostgreSQL 9.0 beta 1:
>
>> psql -U postgres -d test -c "select tablename,
>> pg_
This probably isn't a legitimate bug, but as a precaution
I'm running the following command against PostgreSQL 9.0 beta 1:
psql -U postgres -d test -c "select tablename,
pg_size_pretty(pg_table_size(tablename::regclass)) from pg_tables
order by tablename;"
And getting the following message:
2009/10/16 Robert Haas :
> The fact that this is order-sensitive is just a trap for the unwary
> anyway. I wonder if we ought to implement a flexible options syntax
> like we did for EXPLAIN and COPY, though since I don't know of any new
> options that are needed here maybe it's not worth it.
>
>
2009/10/16 Heikki Linnakangas :
> Thom Brown wrote:
>> Thanks Heikki. You probably already know, but remember to prevent it
>> using FREEZE at all for 8.5+ as according to the documentation it's
>> being deprecated.
>
> It's been documented as
2009/10/16 Heikki Linnakangas :
> Thom Brown wrote:
>> This is either a bug in vacuumdb with it not using the correct order,
>> or postgres shouldn't be paying attention to the order of the
>> keywords. In any case, it doesn't work. I've searched the pos
2009/10/16 Thom Brown :
> Hi,
>
> I've noticed I can't run vacuumdb with ALL FULL VERBOSE and FREEZE.
>
> The error returned is:
>
> vacuumdb: vacuuming of database "killingcupid.co.uk" failed: ERROR:
> syntax error at or near "FREEZE"
> LI
Hi,
I've noticed I can't run vacuumdb with ALL FULL VERBOSE and FREEZE.
The error returned is:
vacuumdb: vacuuming of database "killingcupid.co.uk" failed: ERROR:
syntax error at or near "FREEZE"
LINE 1: VACUUM FULL VERBOSE FREEZE;
The commands I used are:
vacuumdb -afFv
vacuumdb --all --full
32 matches
Mail list logo
