![]() ![]() The difficulty is that PostgreSQL or the applications that launch it can then redirect this stream to all kinds of different places. Selecting stderr instructs PostgreSQL to send log data to the “stderr” (short for “standard error”) output stream most operating systems give every new process by default. This is probably the most common log destination (it’s the default, after all) and can get fairly complicated in itself. You can find instructions for this operation in the PostgreSQL documentation discussing server setup. Anything from a core2duo up with 2GiB (probably 3, depending on how much memory Windows needs) or more RAM should be able to handle this. How that translates to your pc depends on your hardware. You’ll want to tell Windows to expect the log values, and what “event source” they’ll come from. Double that to make the VM powerful enough to also run X and your dev tools. ![]() Event Logįor PostgreSQL systems running on Windows, you can send log entries to the Windows event log. Syslog is often useful, in that it allows administrators to collect logs from many applications into one place, to relieve the database server of logging I/O overhead (which may or may not actually help anything), or any number of other interesting rearrangements of log data.
0 Comments
Leave a Reply. |