spect that it is also doing the same thing for custom and tar
backups as well.
windows filesystem APIs are perfectly happy with forward slashes in
paths, always have been.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sen
> other query is executed.
Lose the "BEGIN" and it will probably work more nicely.
indeed,a 1-5 hour long transaction means VACUUM can't clean up anything
newer than the oldest active transaction, and thats not per database,
thats cluster-wide.
--
john r pierce
ssues building on AIX 6.1 using IBM
XLC. I'm not connected to the build machine at the moment, so I'd have
to dig to find my build instructions (and, of course, XLC is a $$$
compiler).
--
john r pierceN 37, W 122
santa cruz ca
(cost=393.72..393.72 rows=20072 width=32)
-> Seq Scan on lgen_fraud_email o (cost=0.00..393.72
rows=20072 width=32)
without seeing the query, I can only suggest that it appears the LIMIT
is inside of a nested query or something, as it looks like it was
applied prior to additional fi
the user in services.
the SERVICE account ('postgres') needs only 'run as service' privileges.
the user doing the start/stop needs admin privs.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent vi
n
the [bugs] list, would better be discussed on pg-general.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
(OI)(CI)F
then try restarting postgres.
LOCAL_SYSTEM created the files, and owns them.
Oh, the pss-svc user should not be a member of Administrators.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list
things of potential interest in this bug report would be any
unusual or exceptionally large settings in postgresql.conf, is this a 32
bit or 64 bit install
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs ma
something.
maybe add data_directory and config_file to it so it can be a one stop
shop for info useful to help someone...
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To
formance degradations with larger shared buffers.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpr
On 08/15/12 9:02 AM, Valentine Gogichashvili wrote:
On Wed, Aug 15, 2012 at 3:40 PM, John R Pierce <mailto:pie...@hogranch.com>> wrote:
On 08/15/12 6:36 AM, Bruce Momjian wrote:
We warn against making shared buffers > 8GB, and this is
perhaps another
I can't say I remember what it was
called.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 09/09/12 9:31 PM, John R Pierce wrote:
2/ Is anyone working on parallel query execution?
someone presented a FOSS project on the pg-general list the other day
that implements parallel execution using a postgres based engine, but
it only supports fairly simple queries. I can't
On 09/13/12 12:17 PM, te wrote:
FOR r in select distinct(id) from temp
select clean()
what is this selecting records from? what is "temp" ?
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent
e that of the last distinct(id);
since no id is likely to be null or an empty string, the odds are, it
will be returning 999 if there are any records and 0 if there aren't any.
what exactly do you WANT to do?
--
john r pierceN 37, W 122
santa cruz ca
resql-9.0
by doing it this way, you're not editing any files that are under RPM
package management, so you're not going to get bit during updates.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-b
past that
privilege elevation prompt before you can write to Program Files,
install services, and other such similar activities.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@pos
On 10/23/12 4:26 AM, Sree Krishna Priya Kuppa wrote:
Hi Team,
Required a copy of PostgreSQL to install on z/linux i.e Suse Linux
64-bit on OS/390. Please suggest where to get the setup file.
if suse doesn't provide that, you'll likely need to compile your own.
--
joh
. Sure enough, my /etc/hosts is
setting localhost to both 127.0.0.1 and my other IP. Using
`listen_addresses = '127.0.0.1'` fixes the problem.
fix your /etc/hosts thats an artifact of the #@$@# RHEL installer,
if the network isn't properly configured at install time, it love
ts in your /etc/hosts file?
I've seen systems where localhost is 127.0.0.1 and localhost6 is ::1...
RHEL systems come that way.
127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
--
john r pierceN 37, W
On 12/4/2012 1:38 AM, Duggirala, Manikanth (TCS) wrote:
Can you please let us know if PostgreSQL v8.1.11 is compatible with OS
2008 R2 ?
8.1.anything shouldn't be installed today, its an obsolete deprecated
version.
that said, IIRC, there were major issues with versions prior to 8.3 on
On 12/5/2012 4:40 AM, Branka Stancic wrote:
I have problem.
I want to restore only data in database.
In pgAdmin I was backup only data from old database and now i have
backup file backup.sql.
In terminale I want restore only data in new database and I using
command pg_restore -i -h localhost -
On 12/24/2012 2:17 AM, Michael Felt wrote:
*postgresql-8.3.22.tar.bz2* (in progress)
Unpacking the archive has an "error". There are couple references to a
file @LongLink (contents)
$ cat @Long*
postgresql-8.3.22/src/backend/utils/mb/conversion_procs/utf8_and_euc_jis_2004/utf8_and_euc_jis_2004.
On 1/14/2013 3:04 AM, fahar.ab...@enterprisedb.com wrote:
PostgreSQL version: 9.2.2
Operating system: Windows 7, Windows 2003 Server
Description:
I am facing an issue while installed downloaded postgis build.
Version:
PostgreSQL-9.2.2
Steps:
1. Install PostgreSQL 9.2 windows 64 on Windows 7
thats almost
never what you want to do. instead use varchar(100) or character
varying(100) (same thing), or just use text (no length specified), these
formats return just what you store ('joe blow' will return an 8 char
string).
--
john r pierce 37N 122W
somewhere on the middle of the left coast
n the number
of database objects than their size.)
do note this -k option only functions if the old and new cluster are on
the same mount point, so the files can be mv'd
--
john r pierce 37N 122W
somewhere on the middle of the left coast
On 2/15/2013 4:27 PM, Bruce Momjian wrote:
>
>do note this -k option only functions if the old and new cluster are on the
>same mount point, so the files can be mv'd
Actually, hard linked, not moved.
errr, that. right. ;)
--
john r pierce
. This
package supports PostgreSQL ? what version(s) do they recommend? does
it require additional database connectivity components like ODBC, or
NPGSQL or ?
anyways, I don't believe this is a postgresql bug, so doesn't belong on
this list.
--
joh
find the postgres account, and set a
new password via right click... then install the newer postgres and
tell it what that password is.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgr
pgsql-general email list, not as a
'bug report'.
and, there's not enough info here to even begin to guess whats wrong.
maybe you should take this up with your hosting company, if you're
running their OS configuration.
--
john r pierce
ally set a password there.then
tell the postgres installer what you set it to.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscrip
much simpler than changing the
search_path, which is persistent to the connection and likely will
backfire if your apps are changing it to something else.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
query performance?
it wouldn't speed up your example, as your example has to scan every
single row of the whole mess. not sure where Filter: (cid=1) comes
from, since you showed the query as SELECT COUNT(*) FROM dna_strands;
--
john r pierce 37N 12
think you said 268 child partitions. that is, in my experience,
way too many. we try and keep partitions under a few dozen even on our
multi-terabyte tables. 6 months by week is about as far as we go.
with your 10 year data, I'd probably partition by quarter, or something.
older system might not run
optimally on the newer.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
connect as anyone other
than themselves
authentication types are managed via pg_hba.conf
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your
kup software that used
Windows Volume Snapshot Service (VSS).
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
see WHY
the server terminated
but I concurr with Heikki, upgrade to 8.4.latest (currently 8.4.17) and
if this still occurs then figure out why.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
On 4/30/2013 2:55 AM, Bansal, Pradeep wrote:
Also with the debug5 mode the logs are:-
well, I don't see any backend crashes there.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
On 5/12/2013 9:10 AM, Chaya Gilburt wrote:
PostgresSQL Version 8.7.1
hopefully, you mean 8.1.7 ? there never was a 8.7 release, it went up
to 8.4 then rolled over to 9.0
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent
:00:00 postgres: autovacuum
launcher process
postgres 38433 38425 0 01:59 ?00:00:09 postgres: stats
collector process
postgres 39450 38425 85 05:38 ?01:49:02 postgres: postgres
pgbench [local] ALTER TABLE
--
john r pierce 37N 122W
somewhere
by your cluster software.
btw, this is NOT a 'bug report' and does NOT belong on the pgsql-bugs
mail list, you should subscribe to the pgsql-general list for further
discussions.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
m service account is ONLY used in the
Services manager entry for the postgres server, so if you change it in
Local Users when you have an existing postgresql server install, then
you have to find the postgresql service in the Services manager, and
change the password the s
On 5/31/2013 4:29 PM, Gerald Luger wrote:
Shouldn't I expect all results to be 000...0001?
Otherwise it would be
1 != 1?
SQL's BIT type is big endian, a hangover from its IBM mainframe heritage.
--
john r pierce 37N 122W
somewhere on the mid
byte.
IBM numbers bits such that bit 0 is the most significant bit of a word.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
search_path, which is $USER, public... name the
schemas same as the users...
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
On 8/10/2013 4:57 PM, karsten.l...@gmx.ch wrote:
The following bug has been logged on the website:
Bug reference: 8380
Logged by: Karsten Lenz
Email address: karsten.l...@gmx.ch
PostgreSQL version: 9.2.4
Operating system: CentOS 6.4
Description:
Hello,
initdb is ignoring
On 8/30/2013 11:33 AM, Kevin Grittner wrote:
but
you might just be dealing with dead space from deletes and updates.
I would suggest 'likely are' rather than 'might be'.
--
john r pierce 37N 122W
somewhere on the middle of the left
e you can restore it.
CREATE USER "User" WITH PASSWORD 'somekindapassword';
Note the same is true for tablespaces, if you use those.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
service name"
btw, afaik Windows command prompt has no idea what & means.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
orld, where no planning consideration is given towards product
maintenance and updating.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
pg_upgrade to move from 9.1.6 to pg 9.3?
having multiple tablespaces on different mount points complicates
things. I'm not sure how or if pg_upgrade handles that.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
/docs/current/static/bug-reporting.html
oh, direct further correspondence to the bug list,
pgsql-bugs@postgresql.org and not me personally
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-bugs mailing list (pgsql
you're installing, is it tested and supported on win7?
p.s please direct replies to pgsql-bugs@postgresql.org and not me
personally.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-bugs mailing list (
. for instance, at a CMD ('dos') prompt, type the
command,
ECHO %COMSPEC%
and you should get something like...
C:\WINDOWS\system32\cmd.exe
p.s please direct replies to pgsql-bugs@postgresql.org and not me
personally.
--
john r pierce
ux, but I don't believe they
have a MMU, so they can't run a 'regular' linux kernel.
frankly, these don't seem like good candidates for a relational database
server to me.
--
john r pierce 37N 122W
somewhere on the middle of the left
disappear. Two concurrent connections (one from
a console and another from the app) could be contradicting themselves, one
giving the error and the other not.
that sounds like a hardware/platform problem to me more than anything.
maybe in memory cache is getting corrupted or something?
--
john r
301 - 357 of 357 matches
Mail list logo
