hat if the standard NetworkService account is used, it'd be good to
suppress the user account not removed part of the message entirely.
http://stackoverflow.com/q/17394116/398670
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Trai
n:
>
> There are three references to the file @LongLink in the tar file :
> postgresql-8.3.22.tar.bz2
Use GNU tar. Your tar doesn't understand the GNU long-filename
extensions to the tar format.
You'll need GNU make to compile, too.
--
Craig Ringer http://www.2ndQuadran
ckup a `pg_dump`? Or a raw copy of the database directory?
The pg_dump output won't usually provide much information, it's the
actual database on disk that's significant.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sen
27;s codebase;
I'm just aware it's been a reason for the use of fixed length strings in
software in general.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
t certain that advice is sufficient for all contrib modules.
Extensions were created because upgrading DBs that used contrib modules
was a painful mess.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
s. You need to upgrade
the contrib module install to the current version, *then* wrap the
unpackaged contrib module into an extension with "FROM UNPACKAGED".
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Servi
po in the installer. It was recognised and fixed a few weeks
ago; I expect the public installers will have the fix in the next patch
release.
You can work around it in the mean time by editing your system
environment settings to add a SYSTEMDRIVER environment variable.
http://support.microso
able, then merge the
data into the target table using appropriate `UPDATE ... FROM ... WHERE`
and `INSERT ... SELECT ... WHERE` statements.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ttp://archives.postgresql.org/pgsql-general/ . I will not respond to
replies that go directly to me.
--
Craig Ringer
for ages on some systems? Or have there been
previous problems detected and fixed too?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
the CWD explicitly there's no impression given that the
user ever actually specified the whole path in the configuration
anywhere, so it's clearer how the path came to be. It also shows which
part of the path is known-good (since it's the CWD) and which could be
at issue.
--
Craig
t is not valid to provide a scalar
"to_json".
I posted patches to support this functionality - as did several others
as it turns out - and they've all been rejected.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
:
regress=# SELECT ROW(1,'test');
row
--
(1,test)
(1 row)
and output the json:
[1,"test"]
instead of a json object:
regress=# SELECT row_to_json(ROW(1,'test'));
row_to_json
------
{"f1":1,"f2":"test&
ing guidelines linked to on the bug report form you used.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
netheless, thanks for writing it up in so much
detail and chasing it up further - though it'd be nice if you'd
mentioned your earlier post.
I'd love to help, but you've clearly already done a lot of work on this
and I'm not sure I have anything useful to add.
If you do
ontinue to have problems.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 10/16/2012 08:10 PM, Sean Hogan wrote:
On 12-10-16 12:08 AM, Craig Ringer wrote:
On 10/15/2012 11:10 PM, seancompusult wrote:
Does anyone have a solution for people like me who must use Java 5?
I had no problems building current git head of the JDBC driver with
Java SE 5, nor the
/bin:$PATH;
export JAVA_HOME=$HOME/java/jdk1.5.0_22/
ant clean jar
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
se patches just for fun, they're
released to fix bugs and security issues. See:
http://www.postgresql.org/support/versioning/
http://www.postgresql.org/docs/9.0/static/release.html
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to yo
and new cases, if possible.
At least for the new one.
(Please reply to the mailing list, not to me).
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
t, eg:
regress=# SELECT pg_sleep(100);
ERROR: canceling statement due to user request
so I agree that something isn't right here.
Is this something you've been able to reproduce? Or is it a one-off
incident so far?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs
out of disk space? "Invalid argument" would be an odd
error message for that, but who knows with Windows.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
u use a current installer - at least 9.0.10,
preferably 9.2.1.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ork on a larger backup where some \r\n sequences will occur
naturally in compressed binary data. In those you're likely to have a
much, much bigger job ahead of you.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
o stdout when in a non-plain-text
mode on Windows if that's the case.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
st suspect.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
y mistaken. A simple
ROLLBACK throws away any IDs that were obtained from sequences in that
transaction.
If you're saying that the sequence is wrong in that it's LOWER than IDs
present in the table, then that's a problem.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list
iling list. It'd help to
explain what *exactly* you want to know and why. Do you just need the
exact compiler version? Do you need to reproduce the build? Do you need
library / build environment info?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To ma
On 10/11/2012 06:07 PM, Bo Thorbjørn Jensen wrote:
Self-contained case attached.
No crash here on version() = PostgreSQL 9.1.5 on
x86_64-redhat-linux-gnu, compiled by gcc (GCC) 4.7.0 20120507 (Red Hat
4.7.0-5), 64-bit
the steps you've followed, the exact text of the error
messages, etc etc. Use a pastebin site to paste long errors and just put
a link in your email.
Please don't reply to me; make a new post on a more suitable list.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs
18..76.489 rows=4 loops=1)
Filter: (id < 5)
Total runtime: 672.379 ms
(9 rows)
which, if so performs signficiantly worse.
I'm struggling to understand what exactly your complaint is. It's kind
of hard to work out what the intention of the query is in real-worl
or with `NOT EXISTS`. See eg
http://stackoverflow.com/questions/12444142/postgresql-how-to-figure-out-missing-numbers-in-a-column-using-generate-series/12444165#12444165
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
x27;t open it now.
- You edited pg_hba.conf incorrectly, creating syntax errors.
Please do not reply to me, post on -general or SO.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
g clear that demonstrates a problem and helps
isolate which project(s) the problem is in.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
that "Windows 7" doesn't explain much. You need to be
specific, eg "Windows 7 Professional x64 Service Pack 1".
--
Craig Ringer
--
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/18/2012 07:57 AM, Fujii Masao wrote:
If you change the max_connections on the master, you need to take a
fresh backup from the master and start the standby from it.
WTF, really?
What else breaks the replication and forces a re-clone?
--
Craig Ringer
--
Sent via pgsql-bugs mailing
to trace if you set
log_line_prefix to something like:
log_line_prefix = ''
which produces significantly more verbose logs but makes it easier to,
using the pid and txix/vtxid info, work out how different logged
statements fit into transactions.
--
Craig Ringer
--
Sent via pgsql
stgreSQL service.
At a guess, you failed to set the permissions on the data directory to
allow the "postgres" user full control or failed to apply them recursively.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
I have no
starting point for troubleshooting.
Have a look in the Windows event viewer, and see if you can find
anything for the PostgreSQL service there.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.post
client library.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
-training/pgdownload#windows
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
try again. Again, see
http://wiki.postgresql.org/wiki/Running_%26_Installing_PostgreSQL_On_Native_Windows#Common_installation_errors
and http://wiki.postgresql.org/wiki/Troubleshooting_Installation
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make chang
/Troubleshooting_Installation
and send your installer log file.
Please reply to pgsql-bugs@postgresql.org not directly to me.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
e two
- something funky in your OS/system setup
If you were reporting a PostgreSQL bug, you'd want to include things
like *version* *numbers*. See:
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.or
nal 'WSAIoctl' referenced from C:\PROGRAM
FILES (X86)\CODEGEAR\RAD STUDIO\5.0\LIB\DAC105.LIB|CRVioTcp
Does someone know what this could be?
Nothing to do with Pg. You're better off asking somewhere specific to
C++Builder or specific to this "pgdac" tool.
--
Craig Ringer
ect queries
down to make an incorrect query like yours run how you expect.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
sure that the
sort is underspecified. It can't know that the column you've specified
isn't unique, or at least unique within the subset of data you're
working with. It trusts you to know what you want.
The trick is to read the documentation, learn, and test your code wel
On 08/14/2012 11:42 PM, Rikard Pavelic wrote:
On 8.8.2012. 13:30, Craig Ringer wrote:
On 08/08/2012 06:24 PM, rikard.pave...@zg.htnet.hr wrote:
The following bug has been logged on the website:
Bug reference: 7485
Logged by: Rikard Pavelic
Email address: rikard.pave
to do that. Do you?
pushing with --force didn't work?
git push --force origin mybranch
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Argh. Disregard the version comments in my post, I totally failed to
notice the version in the subject line.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
nothing to
do with the problem you linked to.
Please follow up with:
- Your PostgreSQL version
- How you installed PostgeSQL (ie the EnterpriseDB installer, from
source, .zip install)
- The error message you are getting and the command(s) that cause it
- A description of the problem you are h
On 08/08/2012 02:54 PM, John R Pierce wrote:
On 08/07/12 11:10 PM, Craig Ringer wrote:
Please examine the PostgreSQL server logs for error details. I think
they're in /var/lib/pgsql/data/pg_log on CentOS, as that's where they
are on Fedora.
the PGDG rpm/yum repo of 9.1 defaul
ra.
It'd help to know your CentOS version, how you installed PostgreSQL,
etc. Are you using any extensions? PostGIS?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
e psqlODBC sources, patch them
to resolve your issues, and post the patch as a proposed change on the
pgsql-odbc list.
I don't work with ODBC (or Windows very much) so I'm not sure I can be
of much direct help.
--
Craig Ringer
be running 8.3.0,
right? It should be 8.3.something.)
- The full Fedora version
- information about your hardware
- Your PostgreSQL server logs
- Your kernel "dmesg"
--
Craig Ringer
and after
your edits, *what* permissions you changed on the datadir, etc.
--
Craig Ringer
self?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 07/31/2012 07:31 AM, Fábio Hentz Lunkes wrote:
Sorry, all right. It was my mistake.
No worries - thanks for writing back to confirm. That way anyone else
having the issue later will have some idea where to look (or not look at
least).
--
Craig Ringer
be an option to control its
preferred bytea format. It may also be worth turning on log_statement =
'all' in postgresql.conf, starting PgAdmin-III, then looking at the
PostgreSQL logs to see if PgAdmin-III is in fact sending a `SET
bytea_output` command.
--
Craig Ringer
been using PostgreSQL for years now.
It's great.
Only the usage of pg_restore is annoying
Yeah. pg_restore really needs some usability love. I posted a big rant
about it a while ago. It's all about finding the time to actually do
something about it.
--
Craig Ringer
--
Sent via pgs
the table-level grant is
unaffected by a column-level operation.
... so I think you might need to show what's happening in a bit more detail.
Beware that there isn't a big Microsoft Access community here.
--
Craig Ringer
the
leak?
Does the test program I posted behave differently on your system?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 07/27/2012 10:31 AM, Craig Ringer wrote:
Ouch. Sure looks like a leak to me, yeah.
... but it turns out I'm not thinking very straight. I forgot to check
the size of your `shared_buffers' or `work_mem' and forgot to get you to
report `free -m' output after each run to m
On 07/27/2012 01:47 PM, Tom Lane wrote:
Craig Ringer writes:
OK, it's certainly leaking, but not in the same drastic way I was able
to reproduce manually a couple of times earlier. Self-contained test
case attached.
Using HEAD with stock parameters, I don't see any significant
OK, it's certainly leaking, but not in the same drastic way I was able
to reproduce manually a couple of times earlier. Self-contained test
case attached.
$ bash hstore-leak-demo.sh
NOTICE: extension "hstore" already exists, skipping
CREATE EXTENSION
DROP TABLE
CREATE TABLE
CREATE TABLE
INSERT
On 07/27/2012 10:30 AM, Craig Ringer wrote:
Hi all
Here's a fully self contained, automated test case that demonstrates
the leak.
Gah. Except it doesn't now, as shown by the text I pasted. WTF?
I was *definitely* seeing this on my system. What's changed?
Will follow up.
--
leak, but there certainly appears to be one, and you've provided a
pretty clear illustration of it.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Hi all
Here's a fully self contained, automated test case that demonstrates the
leak.
Example output on my system, pasted as quote to stop Thunderbird
mangling it:
$ ./hstore-leak-demo.sh
NOTICE: extension "hstore" already exists, skipping
CREATE EXTENSION
DROP TABLE
CREATE TABLE
CREATE T
Woah. Your email client did something insane, and I cannot read your
message. See below:
On 07/26/2012 09:37 PM, karave...@mail.bg wrote:
- Craig Ringer (ring...@ringerc.id.au), на 26.07.2012 в 11:17 -
On 07/26/2012 09:32 AM, karave...@mail.bg wrote: >> Finally I have
mana
this start happening? At random? After a server crash or power
loss? After an administrative action?
Are you running with fsync=off or using storage that has write caching
enabled?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscri
grow?
What's the output of:
SELECT count(sub.user_id), to_char(AVG(sub.n_prefs), '9.99') FROM (
SELECT user_id, count(name) AS n_prefs FROM old_prefs GROUP BY user_id)
AS sub;
and
SELECT pg_size_pretty(pg_total_relation_size('old_prefs'));
?
--
Craig Ringe
the
pgsql-general mailing list?
It sounds like what you are talking about is table quotas. Try searching
the mailing lists for prior discussion on the topic.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
Encoding as a log line prefix is a terrible idea for all sorts of reasons.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
r-database is useful.
I'm not convinced that a weird and uncommon encoding is the answer. I
guess as an alternative for people for whom it's useful if it's low cost
in terms of complexity/maintenance/etc...
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@post
main issue is just that code needs to be prototyped, cleaned up, and
submitted. So far nobody's cared enough to design it, build it, and get
it through patch review. I've just foolishly volunteered myself to work
on an automated crash-test system for virtual plug-pull testing, so I'm
when that's the case, but it's a good idea anyway.
Personally I think Pg should let this up to the user, but that's the way
it is for now.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ows and see if I can reproduce it.
Ideas anyone? Can someone with a Windows box use pg_ctl to try to start
a new Pg instance against a datadir with an unwritable pg_control ?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
e contact the application's support team for more information.
server starting
I'm not sure why it's crashing here, but you're running such an ancient
version that it's hard to care. If you can reproduce the crash with the
latest 8.3 point release it might be worth a look
Reply-to.
I've cc'd the list.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 07/12/2012 02:24 AM, Patrick Tucker wrote:
BTW I'm using postgresql-9.1-901.jdbc4.jar
Thanks again,
A self-contained test case - a small Java program that connects to a
test DB, runs a query, and reports the result vs what you expected the
result to be - would be helpful.
--
On 07/08/2012 08:46 AM, Balaji A wrote:
Sorry if i came to wrong window ...i just posted my info on the site
and thanks i will reach appropriate group.
Great. Just remember to include a lot more information when you ask for
help on the pgadmin mailing list.
--
Craig Ringer
it crashes, whether you can make it crash at the same point
every time, etc.
Honestly, for PgAdmin you're probably better off seeking help on their
mailing list:
http://www.pgadmin.org/support/list.php
as I'm not sure how many of the PgAdmin folks read pgsql-bugs.
--
Craig Ringer
t the same point
every time, etc.
Honestly, for PgAdmin you're probably better off seeking help on their
mailing list:
http://www.pgadmin.org/support/list.php
as I'm not sure how many of the PgAdmin folks read pgsql-bugs.
--
Craig Ringer
again,
does pg_upgrade then run?
--
Craig Ringer
On 07/05/2012 10:18 PM, Jaime Casanova wrote:
On Thu, Jul 5, 2012 at 1:56 AM, Craig Ringer wrote:
On 07/05/2012 02:05 AM, gary.ha...@gmail.com wrote:
development=# create extension hstore;
ERROR: type "hstore" already exists
First, thanks for the info in the report.
At a guess,
possible to make it work simply and reliably. Since it's a one-off
migration during upgrade, it isn't that big a deal.
If you need help doing this or you have further questions, please ask
for help on the pgsql-general mailing list.
--
Craig Ringer
#x27;m assuming the database "development" was loaded from a dump from an
older version or was binary-upgraded from an older version. If it was
created anew on 9.1, how did the "hstore" type get loaded?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
up and some game came up.
You didn't download it from PostgreSQL.org or EnterpriseDB, then. If you
did, it got intercepted by malware on your computer.
Please provide the URL you downloaded PostgreSQL from and the installer
file name and size.
--
Craig Ringer
--
Sent via pgsql-bugs ma
On 06/27/2012 07:15 PM, Kapil Kr. Khandelwal wrote:
Dear Team
I want to a favour from your side. I want to know, how to run sql
query by command prompt in postgres sql.
psql
http://www.postgresql.org/docs/9.1/static/app-psql.html
--
Craig Ringer
never done any
work in that area at all.
That's what I'm hoping is possible, but like you haven't dug into it yet.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
mitting the report with that info and
have a chance to redact portions if desired.
For now, though, all I'm talking about is a helping-hand web form with
hints about how to find out the exact Windows version, architecture,
antivirus in use, etc. Nothing but a web page with some jQuery code
licy, and how/if antivirus can be detected.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 06/25/2012 11:10 PM, Dave Page wrote:
On Mon, Jun 25, 2012 at 5:41 AM, Craig Ringer wrote:
Dave: Is there any chance the installers link to that page from their error
dialogs, or a static-and-sanitised version of it in docs? If you're ok
updating the installer messages I'll co
're ok updating the installer messages I'll collect up a sanitized
version that doesn't link to other wiki pages (or make it clear they're
external) and convert it for the docs.
--
Craig Ringer
d you install a package they'd produced?
If they're packaging Pg, it sounds like they need to change the paths so
it doesn't tread on the standard installation.
--
Craig Ringer
PM com.apple.launchd:
(com.edb.launchd.postgresql-9.1[3736]) Exited with code: 1
6/18/12 7:42:24.985 PM com.apple.launchd:
(com.edb.launchd.postgresql-9.1) Throttling respawn: Will start in 10
seconds
What's in the system logs (Console.app) ?
The PostgreSQL logs?
--
Craig Ringer
windows small business server 2008 problems?
No known issues with SBS 2008 exist. It should be like any other Windows
server.
Please examine the event viewer to see why the service failed to start,
and post the logs from the data\pg_log folder in your PostgreSQL install
directory.
--
Craig
windows small business server 2008 problems?
No known issues.
Please examine the event viewer to see why the service failed to start,
and post the logs from the data\pg_log folder in your PostgreSQL install
directory.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs
table child_a () inherits (parent)
create table child_b () inherits (parent)
concurrently (two separate connections) results in an error "concurrent
tuple update".
Please copy and paste the full error message.
Which application are you using? psql directly? Something else?
--
Craig Ringe
n x;
ALTER TABLE
regress=# \d
List of relations
Schema | Name | Type | Owner
----+--+---+---
public | test | table | craig
(1 row)
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
1 - 100 of 453 matches
Mail list logo
