On 11 September 2013 07:53, Sergey Shelukhin wrote:
> The query suffers from the auto-lower-casing of unquoted table names,
> which is not ANSI compliant. Technically we could add quotes (and stay
> ANSI), but then MySQL would break without explicitly setting it to use ANSI
> mode, so it's a lose
Hi All,
I am trying to install postgresql-jdbc but facing java error. sun java is
already installed but postgresql-jdbc installing openjdj. please let me
know how to resolve this and if you require any other details.
[root@172-24-1-54 ~]# java -version
java version "1.6.0_33"
Java(TM) SE Runtime
Vivek Singh Raghuwanshi wrote:
> I am trying to install postgresql-jdbc but facing java error.
It would be helpful to know which error you are facing.
Yours,
Laurenz Albe
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postg
patrick keshishian wrote:
> One more "cute" idea that came to me last night. Here is a very
> poor attempt at it by yours truly; keep in mind I'm not a graphics
> artist. This image is for illustration purposes only!
>
> http://sidster.com/gallery/2013/09/10/elephant_paw.sml.jpg
>
> Can you
On Wed, Sep 11, 2013 at 10:19 AM, James Sewell wrote:
> Hello all,
>
> I have a table which makes use of pg_largeobjects. I am inserting rows
> into the table as user1. If I connect to the database as user2 I can SELECT
> data, but can not open the large object for reading (user1 can do this). I
>
java version "1.6.0_33" is already installed but after firing yum install
postgresql-jdbc
java-1.6.0-openjdk is also going to installed as dependencies.
On Wed, Sep 11, 2013 at 1:53 PM, Albe Laurenz wrote:
> Vivek Singh Raghuwanshi wrote:
> > I am trying to install postgresql-jdbc but facing jav
On 9/11/2013 1:47 AM, Vivek Singh Raghuwanshi wrote:
java version "1.6.0_33" is already installed but after firing yum
install postgresql-jdbc
java-1.6.0-openjdk is also going to installed as dependencies.
We never install the RPM of the jdbc driver as its just a single .jar
file... we just b
James Sewell wrote:
> is there any reason to use pg_largeobjects if I am storing data
> under 1GB which doesn't require random reads any more?
If individual large objects might need to be referenced from
multiple locations, it gives you an easy way to do that without
needing to create a new tabl
On Wed, 04 Sep 2013 00:08:52 +0200
Andreas 'ads' Scherbaum wrote:
>
> PostgreSQL folks!
>
> We are looking for the next big thing. Actually, it's a bit smaller: a
> new design for mugs. So far we had big blue elephants, small blue
> elephants, frosty elephants, white SQL code on black mugs ..
Folding to uppercase is according to standard, lowercase no, so in our case
we could expect it to work if we have uppercase tables... in fact, it
should work whether FS is case sensitive or not in MySQL, tables are
created and used uppercase.
Due to presence of a large number of historical installa
Sergey Shelukhin wrote
> Due to presence of a large number of historical installations {doing such
> and such} is not viable.
Yeah, PostgreSQL faces this same issue
If you intend to stay here long, and we hope you do (welcome by the way), it
is customary to bottom-post on these lists.
One ot
On 09/10/2013 11:30 AM, David Johnston wrote:
Steve Crawford wrote
Sorry, I should have included that. The error occurred when an older
client running 8.3.7 (I know, ferreting and finishing upgrades on
clients with old libraries is in progress) on CentOS 5.3 (32-bit). Of
all the machines connect
Hi,
Starting this morning I have been getting out of memory errors from the
postgres autovacuum process. I have searched through previous similar
questions but not found anything other than suggestions to reduce either
'shared_buffers' or 'maintenance_work_mem' but these seem very instance
specifi
Hi,
*I ran into a major problem when I tried to import a backup from 9.1.
into a 9.3 PG.*
I just installed PG 9.3 on a new linux box.
Then I wanted to import a plaintext dump of a DB that was created by
pg_dump of PG 9.1
There are a lot of views that have joins to a subquery in the from-cla
On 09/11/2013 09:53 AM, Andreas wrote:
Hi,
*I ran into a major problem when I tried to import a backup from 9.1.
into a 9.3 PG.*
I just installed PG 9.3 on a new linux box.
Then I wanted to import a plaintext dump of a DB that was created by
pg_dump of PG 9.1
There are a lot of views that have
Andreas-3-2 wrote
> Hi,
>
> *I ran into a major problem when I tried to import a backup from 9.1.
> into a 9.3 PG.*
>
> I just installed PG 9.3 on a new linux box.
> Then I wanted to import a plaintext dump of a DB that was created by
> pg_dump of PG 9.1
>
> There are a lot of views that have
tim truman wrote:
> [ memory usage map ]
There doesn't seem to be any memory context using an unusually large amount of
RAM.
> 522f9128.1151 ERROR: out of memory
> 522f9128.1151 DETAIL: Failed on request of size 336150396.
> 522f9128.1151 CONTEXT: automatic vacuum of table "client.public
Adrian Klaver-3 wrote
> My guess you are seeing this:
>
> http://www.postgresql.org/docs/9.3/interactive/release-9-3.html
>
> Improve view/rule printing code to handle cases where referenced tables
> are renamed, or columns are renamed, added, or dropped (Tom Lane)
>
> Table and column renaming
Am 11.09.2013 21:02, schrieb David Johnston:
Andreas-3-2 wrote
Hi,
*I ran into a major problem when I tried to import a backup from 9.1.
into a 9.3 PG.*
I just installed PG 9.3 on a new linux box.
Then I wanted to import a plaintext dump of a DB that was created by
pg_dump of PG 9.1
There are
Andreas-3-2 wrote
> No, it doesn't work in psql of PG 9.3. I got from EnterpriseDB
Can you please create a minimal self-contained query that exhibits this
behavior and file a bug report?
I quickly cobbled this together - works on 9.0.x
WITH
tblA (a_id, a_val) AS ( VALUES (1::integer, 'one-a'::
Try these too, please:
WITH
tblA (a_id, a_val) AS ( VALUES (1::integer, 'one-1'::varchar) )
, tblB (b_id, b_val) AS ( VALUES (1::integer, 'one-b'::varchar) )
, tblC (c_id, c_val) AS ( VALUES (1::integer, 'one-c'::varchar) )
SELECT *
FROM (
tblA JOIN tblB ON (tblA.a_id = tblB.b_id)
) AS refD
JOI
Hi David,
your 3 examples work as you expected. That is 1+2 work and 3 throws an
error.
I tried to figure out an example and found something peculiar.
The issue arises when there is another join in the subquery after the
one with the reused table alias.
There is no error without this followin
Just another addition...
If I remove the aliases for the tbles flag_1 and flag_2 the problem
still comes up.
So one either has to mind the order of the joins or use unique aliases.
It's really an issue as there are bound to be some queries in
sql-functions or some that get assembled dynamica
Andreas-3-2 wrote
> I never placed a bug-report. :}
> Could you give a hand?
Sure.
PostgreSQL homepage (postgresql.org)
"Report a Bug" link on right-hand side of page.
Fill in the form.
>>>SEND THIS
> droptable if exists sub_tab;
> droptable if exists main_tab;
> droptable
I have been reading few posted comment about the risk for autovacuum for
older postgres liek version 8.
I am currently running 9.2.4. We have a need to terminate any query
running longer than 2 hours. Most of our query should finish within 15
minutes. We don't have very large amount of change
Greetings,
I'm trying to track down some undocumented (or perhaps not well documented)
behavior I'm encountering in regards to custom functions (in plpgsql)
utilizing anyelement and anyarray as arguments and/or return types.
I arrived at this point when I was attempting to write the function
"ANY
I was trying to figure out how to get the following syntax to work:
echo "select pg_start_backup('zfs_snapshot'); \\! zfs snapshot
zroot/zpgsql@test; \\ select pg_stop_backup();" | psql postgres
The above command successfully starts the backup and creates the snapshot
but then fails to stop the b
On Sep 11, 2013, at 4:29 PM, Gregory Haase wrote:
> I was trying to figure out how to get the following syntax to work:
>
> echo "select pg_start_backup('zfs_snapshot'); \\! zfs snapshot
> zroot/zpgsql@test; \\ select pg_stop_backup();" | psql postgres
I do:
psql -c "select pg_start_backup('
Good point on not needing to shell out. I think my process was a mental
holdover from the fact that MySQL releases 'flush tables with read lock' on
client disconnect.
Typically how fast is a crash recovery for a ~1TB database with heavy OTLP
load? Are we talking several seconds, several minutes, s
I took your sample and modified it a bit.
ERROR: table name "tblb" specified more than once
Switch tblB and tblC in the subquery and it works.
WITH
tblA (a_id, a_val) AS ( VALUES (1::integer, 'one-1'::varchar) )
, tblB (b_id, b_val) AS ( VALUES (1::integer, 'one-b'::varchar) )
, tblC (c_id, c
Hey,
This does work, but as I'm using DEFAULT PRIVs to give access to tables it
becomes a (the only) step which can't be done at schema creation time and
has to be done at data insertion time.
It feels to me that ALTER DEFAULT PRIVILEGES should be extended to support
large objects (either by defa
Hi,
I am using pg 9.2.4 and ubuntu 12.04 to set up a pair of pg-Master and pg-Slave
with streaming replication.
The archive_command is enabled and the "rsync" is used in pg-Master to save all
its archived WAL files to the 3rd machine for backup purpose, by default, both
fsync and wal_sync_
Joshua Burns wrote
> CREATE OR REPLACE FUNCTION anyel_anyar(anyelement) RETURNS anyarray AS
> $BODY$
> BEGIN
> RETURN $1;
> END;
> $BODY$ LANGUAGE plpgsql;
Two possible interpretations:
1) must return an array of whatever type is supplied; this is (apparently)
the defined behavior
Joshua Burns wrote
> DROP FUNCTION IF EXISTS anyar_anyel(anyarray);
> CREATE OR REPLACE FUNCTION anyar_anyel(anyarray) RETURNS anyelement AS
> $BODY$
> BEGIN
> RETURN $1;
> END;
> $BODY$ LANGUAGE plpgsql;
Similar to my comment on anyelement->anyarray:
The original goal here is to
On Wed, Sep 11, 2013 at 6:11 PM, ascot.m...@gmail.com
wrote:
> Hi,
>
> I am using pg 9.2.4 and ubuntu 12.04 to set up a pair of pg-Master and
> pg-Slave with streaming replication.
>
> The archive_command is enabled and the "rsync" is used in pg-Master to
> save all its archived WAL files to the 3
Hi everyone;
I have been starting to experiment with the JSON accessors in 9.3. I
immediately found that my preferred use, populating nested composite types,
is not supported. Also of course one cannot manipulate JSON nodes, which
leads to the question of how best to do this. I had some ideas:
Here is a minimal query that demonstrates the problem. In 9.1 it works:
chris=# select * FROM current_user u join (current_user u cross join
current_user v) x on true;
u | u | v
---+---+---
chris | chris | chris
(1 row)
On 9.3 it fails:
ERROR: table name "u" specified mo
37 matches
Mail list logo
